Re: [1/3] 2.6.22-rc3: known regressions with patches v2
From: David Woodhouse
Date: Fri Jun 01 2007 - 15:41:52 EST
On Fri, 2007-06-01 at 14:21 +0200, Michal Piotrowski wrote:
> File systems
>
> Subject : JFFS2 issues
> References :
> http://lists.infradead.org/pipermail/linux-mtd/2007-May/018426.html
> Submitter : Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
> Caused-By : commit 10731f83009e2556f98ffa5c7c2cbffe66dacfb3
> Artem Bityutskiy <Artem.Bityutskiy@xxxxxxxxx>
> Handled-By : Artem Bityutskiy <Artem.Bityutskiy@xxxxxxxxx>
> Patch :
> http://lists.infradead.org/pipermail/linux-mtd/2007-May/018453.html
> Status : patch available
Linus, please pull from git://git.infradead.org/mtd-2.6.git
It contains the fix for the above regression, along with a small number
of other bug fixes -- specifically for XATTR-related oopses, and broken
handling of setattr() in JFFS2. There's actually a couple of things
which aren't strictly bug fixes too, but those are very minor. If you
insist, I could redo the history to omit them, but it's probably cleaner
not to.
Artem Bityutskiy (1):
[JFFS2] Fix buffer length calculations in jffs2_get_inode_nodes()
David Howells (1):
[MTD] generalise the handling of MTD-specific superblocks
David Woodhouse (4):
[JFFS2] Fix BUG() caused by failing to discard xattrs on deleted files.
[JFFS2] Fix potential memory leak of dead xattrs on unmount.
[MTD] Fix error checking after get_mtd_device() in get_sb_mtd functions
[JFFS2] Fix obsoletion of metadata nodes in jffs2_add_tn_to_tree()
Mike Frysinger (1):
[MTD] [MAPS] don't force uclinux mtd map to be root dev
drivers/mtd/Makefile | 3 +-
drivers/mtd/maps/uclinux.c | 5 -
drivers/mtd/mtdsuper.c | 232 ++++++++++++++++++++++++++++++++++++++++++++
fs/jffs2/readinode.c | 22 +++-
fs/jffs2/super.c | 194 ++++---------------------------------
fs/jffs2/xattr.c | 6 +-
include/linux/fs.h | 1 +
include/linux/mtd/super.h | 30 ++++++
8 files changed, 304 insertions(+), 189 deletions(-)
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/