[RTEMS Project] #4538: mutex is not initilaized in jffs2_read_inode

[RTEMS trac]

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

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


Comment:

 Replying to [comment:4 chenjin_zhong]:
 > Replying to [comment:3 Sebastian Huber]:
 > > Yes, the f->sem is an empty structure, it is not initialized, it is
 not used, locked or whatever in RTEMS. This is intentional and not a bug.
 I repeat: **The RTEMS port of JFFS2 does not use a file system internal
 locking. There is a global lock for each JFFS2 instance.**
 >
 > Thank you! I got it. but we Suppose that a GC thread or other
 thread/task and main task calls jffs2_do_readinode simultaneous. a global
 lock for each JFFS2 instance can't work.

 It is not a high performance approach, but it works. See
 `testsuites/fstests/fsjffs2gc01/init.c`.

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