Re: 2.6.18-rc4 jffs2 problems

On 8/17/06, Richard Purdie <[email protected]> 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 <[email protected]>

Acked-by: Josh Boyer <[email protected]>

josh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.18-rc4 jffs2 problems
    • From: Greg KH <[email protected]>

• References:
  • 2.6.18-rc4 jffs2 problems
    • From: Richard Purdie <[email protected]>
  • Re: 2.6.18-rc4 jffs2 problems
    • From: Richard Purdie <[email protected]>

• Prev by Date: Re: [RFC][PATCH 2/9] deadlock prevention core
• Next by Date: Where does NFS client associate the file handle received from server with inode?
• Previous by thread: Re: 2.6.18-rc4 jffs2 problems
• Next by thread: Re: 2.6.18-rc4 jffs2 problems
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]