From: Peter Zijlstra <peterz@infradead.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Chris Mason <clm@fb.com>, Darren Hart <dvhart@linux.intel.com>,
linux-kernel@vger.kernel.org, Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH -next v2] futex: Remove requirement for lock_page in get_futex_key
Date: Mon, 11 Jan 2016 18:47:28 +0100 [thread overview]
Message-ID: <20160111174728.GB6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1452210674-25305-1-git-send-email-dave@stgolabs.net>
On Thu, Jan 07, 2016 at 03:51:14PM -0800, Davidlohr Bueso wrote:
> +++ b/kernel/futex.c
> @@ -520,7 +520,20 @@ again:
> else
> err = 0;
>
> - lock_page(page);
> + /*
> + * The treatment of mapping from this point on is critical. The page
> + * lock protects many things but in this context the page lock
> + * stabilises mapping, prevents inode freeing in the shared
> + * file-backed region case and guards against movement to swap cache.
> + *
> + * Strictly speaking the page lock is not needed in all cases being
> + * considered here and page lock forces unnecessarily serialisation.
> + * From this point on, mapping will be reverified if necessary and
> + * page lock will be acquired only if it is unavoiable.
Making up new words eh?
> + */
> + page = compound_head(page);
> + mapping = READ_ONCE(page->mapping);
> +
> /*
> * If page->mapping is NULL, then it cannot be a PageAnon
> * page; but it might be the ZERO_PAGE or in the gate area or
> } else {
> + struct inode *inode;
> +
> + /*
> + * The associtated futex object in this case is the inode and
> + * the page->mapping must be traversed. Ordinarily this should
> + * be stabilised under page lock but it's not strictly
> + * necessary in this case as we just want to pin the inode, not
> + * update radix tree or anything like that.
> + *
> + * The RCU read lock is taken as the inode is finally freed
> + * under RCU. If the mapping still matches expectations then the
> + * mapping->host can be safely accessed as being a valid inode.
> + */
> + rcu_read_lock();
> + if (READ_ONCE(page->mapping) != mapping ||
> + !mapping->host) {
> + rcu_read_unlock();
> + put_page(page);
> +
> + goto again;
> + }
> + inode = mapping->host;
Don't you want a single load of mapping->host? Could it not have become
NULL just between these two loads?
> +
> + /*
> + * Take a reference unless it is about to be freed. Previously
> + * this reference was taken by ihold under the page lock
> + * pinning the inode in place so i_lock was unnecessary. The
> + * only way for this check to fail is if the inode was
> + * truncated in parallel so warn for now if this happens.
> + *
> + * We are not calling into get_futex_key_refs() in file-backed
> + * cases, therefore a successful atomic_inc return below will
> + * guarantee that get_futex_key() will continue to imply MB (B).
> + */
> + if (WARN_ON(!atomic_inc_not_zero(&inode->i_count))) {
ONCE?
> + rcu_read_unlock();
> + put_page(page);
> +
> + goto again;
> + }
> +
> + /* Should be impossible but lets be paranoid for now */
> + BUG_ON(inode->i_mapping != mapping);
> +
> key->both.offset |= FUT_OFF_INODE; /* inode-based key */
> - key->shared.inode = mapping->host;
> + key->shared.inode = inode;
> key->shared.pgoff = basepage_index(page);
> + rcu_read_unlock();
> }
prev parent reply other threads:[~2016-01-11 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 23:51 Davidlohr Bueso
2016-01-11 17:47 ` Peter Zijlstra [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=20160111174728.GB6344@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=clm@fb.com \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@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
all inboxes | Powered by JetHome®