From: "Martin Schwidefsky" <schwidefsky@googlemail.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Nick Piggin" <nickpiggin@yahoo.com.au>,
benh@kernel.crashing.org, cotte@de.ibm.com,
"Zan Lynx" <zlynx@acm.org>, "Ryan Hope" <rmh3093@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: Lockless/Get_User_Pages_Fast causes Xorg 1.4.99.* to lock
Date: Mon, 7 Jul 2008 13:08:53 +0200 [thread overview]
Message-ID: <6e0cfd1d0807070408ybea080ewa75ed1f1a8f9326c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807071134090.21480@blonde.site>
On Mon, Jul 7, 2008 at 12:39 PM, Hugh Dickins <hugh@veritas.com> wrote:
> On Mon, 7 Jul 2008, Nick Piggin wrote:
>>
>> I think we need a similar fix for s390 too. If so, then it really should
>> get into 2.6.26, but this late in the release, I hope an s390 maintainer
>> might be able to test and verify the fix?
>
> Wow, yes, I hadn't realized s390 is ahead of the game there: glad you're
> back to spot that. But yes, we'd prefer maintainer to confirm and push.
>
>
> [PATCH]] s390: protect _PAGE_SPECIAL bit against mprotect
>
> Stop mprotect's pte_modify from wiping out the s390 pte_special bit, which
> caused oops thereafter when vm_normal_page thought X's abnormal was normal.
>
> Signed-off-by: Nick Piggin <npiggin@suse.de>
> Acked-by: Hugh Dickins <hugh@veritas.com>
s390 will definitely need this. Loosing the pte special bit is not
good. I'll prepate
a please pull right away. Thanks of pointing this out.
--
blue skies,
Martin
next prev parent reply other threads:[~2008-07-07 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 6:26 Ryan Hope
2008-07-04 16:29 ` Zan Lynx
2008-07-04 20:29 ` Hugh Dickins
2008-07-05 5:26 ` Ryan Hope
2008-07-06 21:03 ` Zan Lynx
2008-07-07 7:01 ` Nick Piggin
2008-07-07 7:55 ` Nick Piggin
2008-07-07 8:06 ` Nick Piggin
2008-07-07 10:39 ` Hugh Dickins
2008-07-07 11:08 ` Martin Schwidefsky [this message]
2008-07-07 11:39 ` Nick Piggin
2008-07-07 12:02 ` Hugh Dickins
2008-07-07 15:43 ` Carsten Otte
2008-07-07 16:16 ` Ryan Hope
2008-07-07 16:38 ` Carsten Otte
2008-07-07 17:01 ` Ryan Hope
2008-07-07 17:48 ` Hugh Dickins
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=6e0cfd1d0807070408ybea080ewa75ed1f1a8f9326c@mail.gmail.com \
--to=schwidefsky@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cotte@de.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rmh3093@gmail.com \
--cc=zlynx@acm.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®