From: Matthew Wilcox <matthew@wil.cx>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] dmapools: protect page_list walk in show_pools()
Date: Tue, 23 Jun 2009 08:46:08 -0600 [thread overview]
Message-ID: <20090623144608.GE19977@parisc-linux.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0906231634210.2767@localhost.localdomain>
On Tue, Jun 23, 2009 at 04:41:14PM +0200, Thomas Gleixner wrote:
> show_pools() walks the page_list of a pool w/o protection against the
> list modifications in alloc/free. Take pool->lock to avoid stomping
> into nirvana.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Looks right to me. We're already holding pools_lock here, but pools_lock
doesn't protect against the page_list.
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
I don't have a tree for dmapool work ... might as well go in through
Andrew, I suppose?
> ---
> diff --git a/mm/dmapool.c b/mm/dmapool.c
> index b1f0885..3df0637 100644
> --- a/mm/dmapool.c
> +++ b/mm/dmapool.c
> @@ -86,10 +86,12 @@ show_pools(struct device *dev, struct device_attribute *attr, char *buf)
> unsigned pages = 0;
> unsigned blocks = 0;
>
> + spin_lock_irq(&pool->lock);
> list_for_each_entry(page, &pool->page_list, page_list) {
> pages++;
> blocks += page->in_use;
> }
> + spin_unlock_irq(&pool->lock);
>
> /* per-pool info, no real statistics yet */
> temp = scnprintf(next, size, "%-16s %4u %4Zu %4Zu %2u\n",
>
>
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2009-06-23 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 14:41 [PATCH] dmapools: protect page_list walk in show_pools() Thomas Gleixner
2009-06-23 14:46 ` Matthew Wilcox [this message]
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=20090623144608.GE19977@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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