From: Pekka Paalanen <pq@iki.fi>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Stuart Bennett <stuart@freedesktop.org>,
Christoph Bumiller <e0425955@student.tuwien.ac.at>,
Shinpei KATO <shinpei@il.is.s.u-tokyo.ac.jp>,
nouveau@lists.freedesktop.org, x86@kernel.org
Subject: Re: [PATCH] kmmio/mmiotrace: fix double free of kmmio_fault_pages
Date: Sat, 5 Jun 2010 20:29:33 +0300 [thread overview]
Message-ID: <20100605202933.7a650c62@daedalus.pq.iki.fi> (raw)
In-Reply-To: <20100605164919.GA2816@joi.lan>
On Sat, 5 Jun 2010 18:49:42 +0200
Marcin Slusarz <marcin.slusarz@gmail.com> wrote:
> After every iounmap mmiotrace has to free kmmio_fault_pages, but
> it can't do it directly, so it defers freeing by RCU.
>
> It usually works, but when mmiotraced code calls ioremap-iounmap
> multiple times without sleeping between (so RCU won't kick in and
> start freeing) it can be given the same virtual address, so at
> every iounmap mmiotrace will schedule the same pages for release.
> Obviously it will explode on second free.
>
> Fix it by marking kmmio_fault_pages which are scheduled for
> release and not adding them second time.
>
> Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
> Cc: Pekka Paalanen <pq@iki.fi>
> Cc: Stuart Bennett <stuart@freedesktop.org>
Excellent work! Unfortunately I cannot review this patch
right now, I am sick. The description sounds good, though,
and I have no objections.
Thank you very much!
> ---
> arch/x86/mm/kmmio.c | 16 +++++++++++++---
> 1 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/mm/kmmio.c b/arch/x86/mm/kmmio.c
> index 5d0e67f..e5d5e2c 100644
> --- a/arch/x86/mm/kmmio.c
> +++ b/arch/x86/mm/kmmio.c
> @@ -45,6 +45,8 @@ struct kmmio_fault_page {
> * Protected by kmmio_lock, when linked into
> kmmio_page_table. */
> int count;
> +
> + bool scheduled_for_release;
> };
>
> struct kmmio_delayed_release {
> @@ -398,8 +400,11 @@ static void
> release_kmmio_fault_page(unsigned long page, BUG_ON(f->count < 0);
> if (!f->count) {
> disarm_kmmio_fault_page(f);
> - f->release_next = *release_list;
> - *release_list = f;
> + if (!f->scheduled_for_release) {
> + f->release_next = *release_list;
> + *release_list = f;
> + f->scheduled_for_release = true;
> + }
> }
> }
>
> @@ -471,8 +476,10 @@ static void remove_kmmio_fault_pages(struct
> rcu_head *head) prevp = &f->release_next;
> } else {
> *prevp = f->release_next;
> + f->release_next = NULL;
> + f->scheduled_for_release = false;
> }
> - f = f->release_next;
> + f = *prevp;
> }
> spin_unlock_irqrestore(&kmmio_lock, flags);
>
> @@ -510,6 +517,9 @@ void unregister_kmmio_probe(struct
> kmmio_probe *p) kmmio_count--;
> spin_unlock_irqrestore(&kmmio_lock, flags);
>
> + if (!release_list)
> + return;
> +
> drelease = kmalloc(sizeof(*drelease), GFP_ATOMIC);
> if (!drelease) {
> pr_crit("leaking kmmio_fault_page objects.\n");
> --
> 1.7.1
>
>
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2010-06-05 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 16:49 Marcin Slusarz
2010-06-05 17:29 ` Pekka Paalanen [this message]
2010-06-05 19:33 ` Marcin Slusarz
2010-06-05 20:45 ` Pekka Paalanen
2010-06-07 13:33 ` Ingo Molnar
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=20100605202933.7a650c62@daedalus.pq.iki.fi \
--to=pq@iki.fi \
--cc=e0425955@student.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=nouveau@lists.freedesktop.org \
--cc=shinpei@il.is.s.u-tokyo.ac.jp \
--cc=stuart@freedesktop.org \
--cc=x86@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®