From: Ed Cashin <ecashin@coraid.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] aoe: adjust ref of head for compound page tails
Date: Wed, 7 Aug 2013 17:12:36 -0400 [thread overview]
Message-ID: <8DFEA276-4EE1-44B4-9669-5634631D7BBC@coraid.com> (raw)
In-Reply-To: <20130807135804.e62b75f6986e9568ab787562@linux-foundation.org>
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.
I don't have a counter in the driver to track how often zero-count pages show up in bios, so I don't know how common it is these days. I would have been motivated to look if I had gotten the impression that there was any interest in identifying and eliminating cases where zero-count pages were being used in bios.
--
Ed Cashin
ecashin@coraid.com
next prev parent reply other threads:[~2013-08-07 21:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 1:29 [PATCH] aoe: respect compound page reference tracking expectations Ed Cashin
2013-08-02 1:29 ` [PATCH] aoe: adjust ref of head for compound page tails Ed Cashin
2013-08-07 20:58 ` Andrew Morton
2013-08-07 21:12 ` Ed Cashin [this message]
2013-08-07 21:18 ` Andrew Morton
2013-08-07 21:27 ` Andrew Morton
2013-08-07 23:41 ` Ed Cashin
2013-08-07 23:48 ` Ed Cashin
2013-08-07 23:51 ` Andrew Morton
2013-08-07 21:00 ` Andrew Morton
2013-08-07 21:21 ` Ed Cashin
2013-08-07 21:26 ` Andrew Morton
2013-08-07 23:27 ` Ed Cashin
2013-08-07 23:35 ` Andrew Morton
2013-08-07 23:54 ` Ed Cashin
2013-08-08 0:05 ` Andrew Morton
2013-08-08 0:50 ` Ed Cashin
2013-08-08 19:56 ` Andrew Morton
2013-08-08 21:02 ` Ed Cashin
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=8DFEA276-4EE1-44B4-9669-5634631D7BBC@coraid.com \
--to=ecashin@coraid.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®