From: Andrew Morton <akpm@linux-foundation.org>
To: Ed Cashin <ecashin@coraid.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] aoe: adjust ref of head for compound page tails
Date: Wed, 7 Aug 2013 14:27:55 -0700 [thread overview]
Message-ID: <20130807142755.5cd89e02e4286f7dca88b80d@linux-foundation.org> (raw)
In-Reply-To: <20130807141835.533816143f8b37175c50d58d@linux-foundation.org>
On Wed, 7 Aug 2013 14:18:35 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 7 Aug 2013 17:12:36 -0400 Ed Cashin <ecashin@coraid.com> wrote:
>
> >
> > On Aug 7, 2013, at 4:58 PM, Andrew Morton wrote:
> >
> > > On Thu, 1 Aug 2013 21:29:59 -0400 Ed Cashin <ecashin@coraid.com> wrote:
> > >
> > >> As discussed previously,
> > >
> > > I think I missed that.
> > >
> > >> the fact that some users of the block
> > >> layer provide bios that point to pages with a zero _count means
> > >> that it is not OK for the network layer to do a put_page on the
> > >> skb frags during an skb_linearize, so the aoe driver gets a
> > >> reference to pages in bios and puts the reference before ending
> > >> the bio. And because it cannot use get_page on a page with a
> > >> zero _count, it manipulates the value directly.
> > >
> > > Eh? What code is putting count==0 pages into bios? That sounds very
> > > weird and broken.
> >
> > I thought so in 2007 but couldn't solicit a clear "this is wrong" consensus from the discussion.
> >
> > http://article.gmane.org/gmane.linux.kernel/499197
> > https://lkml.org/lkml/2007/1/19/56
> > https://lkml.org/lkml/2006/12/18/230
> >
> > We were seeing zero-count pages in bios from XFS, but Christoph Hellwig pointed out that kmalloced pages can also come from ext3 when it's doing log recovery, and they'll have zero page counts.
>
> aiiee!
>
> It is (I suppose) reasonable to put kmalloced memory into a BIO's page
> array. And it is perfectly reasonable for a user of that bio to do a
> get_page/put_page against that page. It is utterly unreasonable for
> the damn page to get freed as a result!
>
> I'd claim that slab is broken. The page is in use, so it should have an
> elevated refcount, full stop.
>
err, no. slab.c uses alloc_pages(), so the underlying page indeed has
a proper refcount. I'm still not understanding how this situation comes
about.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-08-07 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1375320764.git.ecashin@coraid.com>
[not found] ` <0c8aff39249c1da6b9cc3356650149d065c3ebd2.1375320764.git.ecashin@coraid.com>
[not found] ` <20130807135804.e62b75f6986e9568ab787562@linux-foundation.org>
[not found] ` <8DFEA276-4EE1-44B4-9669-5634631D7BBC@coraid.com>
2013-08-07 21:18 ` Andrew Morton
2013-08-07 21:27 ` Andrew Morton [this message]
2013-08-07 23:41 ` Ed Cashin
2013-08-07 23:48 ` Ed Cashin
2013-08-07 23:51 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130807142755.5cd89e02e4286f7dca88b80d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ecashin@coraid.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox