mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Mel Gorman <mgorman@techsingularity.net>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Chris Mason <clm@fb.com>, Darren Hart <dvhart@linux.intel.com>,
	Hugh Dickins <hughd@google.com>,
	dave@stgolabs.net, linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/2] futex: lockless get_futex_key
Date: Tue,  9 Feb 2016 11:15:12 -0800	[thread overview]
Message-ID: <1455045314-8305-1-git-send-email-dave@stgolabs.net> (raw)

This is the continuation of the original patch, except with Ingo's
feedback about the ordering comments we have and how we reference
them throughout the code. Please consider for v4.6.

Thanks!

Changes from v5:
- Added patch 1 (Ingo).

Changes from v4:
- Integrated feedback from Hugh, specifically:
   * check for page->mapping change with page lock held when
     detecting shm race.
   * move inode assign, if the mapping still matches what
     we expect should we have a valid inode.
   * move iput out of rcu lock.

Changes from v3:
- Redo mapping sanity check, now do not halt the kernel.

Changes from v2:

- Minor adjustments by peterz.
- Applies on top of -next-20160118

Changes from v1:
- Remove unnecesary mb, as atomic_inc returning does what we need.
- Fix bogus mapping load.
- Minor code cleanups/comments.


Davidlohr Bueso (2):
  futex: Rename barrier references in ordering guarantees
  futex: Remove requirement for lock_page in get_futex_key

 kernel/futex.c | 131 ++++++++++++++++++++++++++++++++++++++++++++++-----------
 1 file changed, 107 insertions(+), 24 deletions(-)

-- 
2.1.4

             reply	other threads:[~2016-02-09 19:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 19:15 Davidlohr Bueso [this message]
2016-02-09 19:15 ` [PATCH v6 1/2] futex: Rename barrier references in ordering guarantees Davidlohr Bueso
2016-02-17 12:25   ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2016-02-09 19:15 ` [PATCH v6 2/2] futex: Remove requirement for lock_page in get_futex_key Davidlohr Bueso
2016-02-17 12:26   ` [tip:locking/core] futex: Remove requirement for lock_page() in get_futex_key() tip-bot for 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=1455045314-8305-1-git-send-email-dave@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=bigeasy@linutronix.de \
    --cc=clm@fb.com \
    --cc=dvhart@linux.intel.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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®