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

 On Fri, Jun 02, Andrew Morton wrote:

> On Fri, 2 Jun 2006 21:37:02 +0200
> Olaf Hering <[email protected]> wrote:
> 
> > > I'd suggest you run SetPagePrivate() and SetPageChecked() on the locked
> > > page and implement a_ops.releasepage(), which will fail if PageChecked(),
> > > and will succeed otherwise:
> > 
> > No leak without tweaking PG_private.
> 
> Odd.  That would imply that PG_private is being left set somehow (it will
> make the page unreclaimable).  But I don't see it.
> 
> Plus if we have lots of PagePrivate() pages floating about you should see
> your ->releasepage() being called.

The change from Chris leaks as well, but very very slowly.

Please wait while I dig into the page states...
-
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:
  • [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]>
  • [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]>
  • Re: [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]>
  • Re: [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]>
  • Re: [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: [patch] Declare explicit, hardware based lock ranking in serio
• Next by Date: Re: [PATCH 07/11] the latest consensus libata resume fix
• Previous by thread: Re: [PATCH] cramfs corruption after BLKFLSBUF on loop device
• Next by thread: Re: [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]