From: Willy Tarreau <w@1wt.eu>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Hugh Dickins <hughd@google.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [34-longterm 167/179] futex: Fix regression with read only mappings
Date: Tue, 15 May 2012 20:55:13 +0200 [thread overview]
Message-ID: <20120515185513.GA13685@1wt.eu> (raw)
In-Reply-To: <20120515160250.GA17760@windriver.com>
On Tue, May 15, 2012 at 12:02:50PM -0400, Paul Gortmaker wrote:
> [Re: [34-longterm 167/179] futex: Fix regression with read only mappings] On 15/05/2012 (Tue 12:51) Peter Zijlstra wrote:
>
> > On Mon, 2012-05-14 at 21:38 -0700, Hugh Dickins wrote:
> > > I don't know: I'm not NAKking it, I'm just waving a reddish flag,
> > > and hoping that Peter will remember more, and have something more
> > > constructive to say, than I can think of at this moment.
> >
> > Ha! you're very optimistic :-)
> >
> > going by git log kernel/futex.c on a recent kernel the proposed patch
> > should indeed be followed by your patch, but I can't seem to find more
> > relevant patches.
>
> Thanks a lot guys. That is a dependency I'd never have come up with.
>
> Willy -- this is probably of interest to you as well. Hugh says that
> commit e6780f7243 ("futex: Fix uninterruptible loop due to gate_area")
> should be used if 9ea71503a8 ("futex: Fix regression with read only
> mappings") is used. The v2.6.32.46 added 9ea71503a8 (as d64ec7bb),
> but I don't see a cherry pick of e6780f7243 in any v2.6.32.x yet.
>
> Greg already applied it to 3.0.16 and 3.1.8 and it appeared in v3.2
> by default, so no other active stable releases need to worry.
>
> I had to change page_mapping --> page, since the 2.6.34 baseline does
> not have a5b338f2b0b1ff73 ("thp: update futex compound knowledge")
> [added to v2.6.38] which introduces the shadow variable page_mapping.
Thank you very much Paul, I'm queuing it then. I hope to have some time for
a new -32 review soon, probably next week-end.
Cheers,
Willy
next prev parent reply other threads:[~2012-05-15 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337048075-6132-1-git-send-email-paul.gortmaker@windriver.com>
2012-05-15 3:01 ` [34-longterm 000/179] v2.6.34.12 longterm review Paul Gortmaker
[not found] ` <1337048075-6132-168-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <alpine.LSU.2.00.1205142126180.2196@eggly.anvils>
[not found] ` <1337079117.27694.28.camel@twins>
2012-05-15 16:02 ` [34-longterm 167/179] futex: Fix regression with read only mappings Paul Gortmaker
2012-05-15 18:55 ` Willy Tarreau [this message]
[not found] ` <1337048075-6132-180-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <20120515154455.39cfbad2@pyramind.ukuu.org.uk>
[not found] ` <20120515154743.04879bde@pyramind.ukuu.org.uk>
2012-05-15 16:03 ` [34-longterm 179/179] x86/PCI: do not tie MSI MS-7253 use_crs quirk to BIOS version Paul Gortmaker
[not found] ` <1337048075-6132-75-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <20120515050221.GA4292@burratino>
2012-05-15 16:33 ` [34-longterm 074/179] xen: Use IRQF_FORCE_RESUME Paul Gortmaker
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=20120515185513.GA13685@1wt.eu \
--to=w@1wt.eu \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).