| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <625fc13d0608191834r19ce12e5raccbae011d67c25e@mail.gmail.com> Date: Sat, 19 Aug 2006 20:34:46 -0500 From: "Josh Boyer" <jwboyer@...il.com> To: "Richard Purdie" <rpurdie@...ys.net> Cc: linux-mtd <linux-mtd@...ts.infradead.org>, "Thomas Gleixner" <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, "Greg KH" <greg@...ah.com>, "David Woodhouse" <dwmw2@...radead.org> Subject: Re: 2.6.18-rc4 jffs2 problems On 8/17/06, Richard Purdie <rpurdie@...ys.net> wrote: > Read the return value before we release the nand device otherwise the > value can become corrupted by another user of chip->ops, ultimately > resulting in filesystem corruption. > We have multiple confirmations that this patch fixes the issue reported. I agree it should go in 2.6.18. Greg, can you add this to your tree? > Signed-off-by: Richard Purdie <rpurdie@...ys.net> Acked-by: Josh Boyer <jwboyer@...il.com> josh - 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