Re: [PATCH] cramfs corruption after BLKFLSBUF on loop device

On Thu, 1 Jun 2006 12:12:00 -0700
Andrew Morton <[email protected]> wrote:

> I'd have
> thought that it'd be appropriate to take i_mutex while running
> invalidate_inode_pages().

Let me add: it'd be appropriate, but also difficult -
invalidate_inode_pages() is called from all sorts of contexts, including
inside spinlock.

A quickie fix would be to take i_mutex at the top level, on entry to the
ioctl.  But that'll only fix the BLKFLSBUF case.

-
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/

---

• References:
  • cramfs corruption after BLKFLSBUF on loop device
    • From: Olaf Hering <[email protected]>
  • Re: cramfs corruption after BLKFLSBUF on loop device
    • From: Olaf Hering <[email protected]>
  • [PATCH] cramfs corruption after BLKFLSBUF on loop device
    • From: Olaf Hering <[email protected]>
  • Re: [PATCH] cramfs corruption after BLKFLSBUF on loop device
    • From: Andrew Morton <[email protected]>

• Prev by Date: RE: pci_enable_msix throws up error
• Next by Date: Re: [PATCH] ipaq.c bugfixes
• Previous by thread: Re: [PATCH] cramfs corruption after BLKFLSBUF on loop device
• Next by thread: [PATCH] cramfs corruption after BLKFLSBUF on loop device
• 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]