Oops in mounting jffs2 (jffs2_get_ino_cache())

Vipin Malik vipin at embeddedlinuxworks.com
Fri May 2 12:03:06 EDT 2003


May I humbly suggest that this is the type of info one should comment in 
the relevant place in the code.

Just a suggestion. I am happy someone has already fixed the problem though!

Regards,

Vipin

At 04:24 PM 5/2/2003 +0100, David Woodhouse wrote:
>On Fri, 2003-05-02 at 16:18, Dave Ellis wrote:
> > I think it is OK. Even during mount the inode crc is checked in
> > jffs2_scan_inode_node() before adding a _new_ inode to the cache (it
> > checks only if the inode isn't already in the cache). So every inode
> > number in the cache must have at least one valid inode node, which
> > keeps the bad inodes like #0xffffffef and #0xffffffff out of the cache.
> >
> > The inode numbers that change c->highest_ino all come from the inode
> > cache, so it should never see the bad values.
>
>You're right -- evidently I did think of this at the time :)
>
>--
>dwmw2




More information about the linux-mtd mailing list