[RTEMS Project] #4537: mutex is not initilaized in jffs2_new_inode

RTEMS trac trac at rtems.org
Thu Oct 28 05:20:02 UTC 2021


#4537: mutex is not initilaized in jffs2_new_inode
---------------------------+----------------------
 Reporter:  chenjin_zhong  |       Owner:  (none)
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:  5.1
Component:  admin          |     Version:  5
 Severity:  normal         |  Resolution:  invalid
 Keywords:                 |  Blocked By:
 Blocking:                 |
---------------------------+----------------------
Changes (by Sebastian Huber):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Thanks for your interest in the RTEMS port of JFFS2. If you have
 questions, then you could also ask them on the devel at rtems.org mailing
 list. The RTEMS port of JFFS2 does not use a file system internal locking.
 There is a global lock for each JFFS2 instance:
 {{{#!c
 static void rtems_jffs2_do_lock(struct super_block *sb)
 {
         rtems_recursive_mutex_lock(&sb->s_mutex);
 }

 static void rtems_jffs2_do_unlock(struct super_block *sb)
 {
         rtems_recursive_mutex_unlock(&sb->s_mutex);
 }
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/4537#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project


More information about the bugs mailing list