[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091123131613.GA14619@oksana.dev.rtsoft.ru>
Date: Mon, 23 Nov 2009 16:16:13 +0300
From: Anton Vorontsov <avorontsov@...mvista.com>
To: David Woodhouse <dwmw2@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Neil Brown <neilb@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>
Subject: Re: [PATCH] jffs2: Fix memory corruption in
jffs2_read_inode_range()
On Sun, Nov 22, 2009 at 10:20:59AM +0000, David Woodhouse wrote:
> On Fri, 2009-11-20 at 12:45 -0700, Anton Vorontsov wrote:
> > + if (pg->index > ((i_size_read(inode) - 1) >> PAGE_CACHE_SHIFT)) {
> > + ret = 0;
> > + memset(pg_buf, 0, PAGE_CACHE_SIZE);
> > + } else {
> > + ret = jffs2_read_inode_range(c, f, pg_buf,
> > + pg->index << PAGE_CACHE_SHIFT, PAGE_CACHE_SIZE);
> > + }
>
> Thank you for the excellent diagnosis and the patch.
>
> I think I'd prefer to fix it a little differently though -- I would be
> happier to make jffs2_read_inode_range() cope with out-of-file reads,
> rather than adding this special case where we don't call it.
>
> That way we aren't at all susceptible to potential races between the
> VFS-maintained i_size and our own internal fragtree handling. And
> jffs2_read_inode_range() already handles the memset to zero for various
> other reasons anyway.
>
> Does this patch look OK to you? It seems to work on the test cases I've
> tried.
Yep, it looks good (and works).
Thanks David!
--
Anton Vorontsov
email: cbouatmailru@...il.com
irc://irc.freenode.net/bd2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists