From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Mel Gorman <mgorman@suse.de>, lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
kirill@shutemov.name
Subject: Re: [patch] futex: Fix v4.6+ ltp futex_wait04 regression
Date: Mon, 6 Jun 2016 15:07:19 +0200 [thread overview]
Message-ID: <20160606130719.GA30935@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1465206041.6397.14.camel@gmail.com>
On Mon, Jun 06, 2016 at 11:40:41AM +0200, Mike Galbraith wrote:
> --- a/kernel/futex.c
> +++ b/kernel/futex.c
> @@ -469,7 +469,7 @@ get_futex_key(u32 __user *uaddr, int fsh
> {
> unsigned long address = (unsigned long)uaddr;
> struct mm_struct *mm = current->mm;
> - struct page *page;
> + struct page *page, *pinned = NULL;
> struct address_space *mapping;
> int err, ro = 0;
>
> @@ -530,8 +530,18 @@ get_futex_key(u32 __user *uaddr, int fsh
> * considered here and page lock forces unnecessarily serialization
> * From this point on, mapping will be re-verified if necessary and
> * page lock will be acquired only if it is unavoidable
> - */
> + *
> + * If we're dealing with a compound page, save our reference to the
> + * page we locked in memory above, and take a new reference on the
> + * page head, dropping the previously pinned page reference on retry.
> + */
> + if (unlikely(pinned && page != pinned))
> + put_page(pinned);
> + pinned = page;
> page = compound_head(page);
> + if (unlikely(pinned != page))
> + get_page(page);
Not needed, since {get,put}_page() explicitly use compound_head() to
track the reference count on.
> +
> mapping = READ_ONCE(page->mapping);
>
> /*
> @@ -560,12 +570,14 @@ get_futex_key(u32 __user *uaddr, int fsh
> lock_page(page);
> shmem_swizzled = PageSwapCache(page) || page->mapping;
> unlock_page(page);
> - put_page(page);
>
> - if (shmem_swizzled)
> + if (shmem_swizzled) {
> + put_page(page);
> goto again;
> + }
>
> - return -EFAULT;
> + err = -EFAULT;
> + goto out;
This also simplifies away
> }
>
> /*
> @@ -654,12 +666,14 @@ get_futex_key(u32 __user *uaddr, int fsh
>
> key->both.offset |= FUT_OFF_INODE; /* inode-based key */
> key->shared.inode = inode;
> - key->shared.pgoff = basepage_index(page);
> + key->shared.pgoff = basepage_index(pinned);
But this seems to be the actual fix; because while I think the compound
page cannot change from under us, it can change between futex
invocations, and then having a key change is _bad_.
But someone other than me would have to concurr, its been too long since
I looked at all this compound muck.
> rcu_read_unlock();
> }
>
> out:
> put_page(page);
> + if (unlikely(pinned != page))
> + put_page(pinned);
and that too can go.
> return err;
> }
next prev parent reply other threads:[~2016-06-06 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 9:40 [patch] futex: Fix v4.6+ ltp futex_wait04 regression Mike Galbraith
2016-06-06 13:07 ` Peter Zijlstra [this message]
2016-06-06 13:34 ` Mike Galbraith
2016-06-06 13:46 ` Mike Galbraith
2016-06-07 10:50 ` Mel Gorman
2016-06-07 11:20 ` Mel Gorman
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=20160606130719.GA30935@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/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