From: Zan Lynx <zlynx@acm.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ryan Hope <rmh3093@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Lockless/Get_User_Pages_Fast causes Xorg 1.4.99.* to lock
Date: Sun, 06 Jul 2008 15:03:06 -0600 [thread overview]
Message-ID: <4871330A.3030400@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0807042112130.16912@blonde.site>
Hugh Dickins wrote:
> On Fri, 4 Jul 2008, Zan Lynx wrote:
[cut]
> Useful info, thank you; even more useful was the Code line in your attachment
>
>> [ 269.224557] Code: 00 00 48 b9 00 00 00 00 00 e2 ff ff 48 21 d8 48 c1 e8 0c 48 8d 14 c5 00 00 00 00 48 c1 e0 06 48 29 d0 48 01 c1 0f 84 10 ff ff ff <48> 8b 01 48 89 ca f6 c4 40 74 04 48 8b 51 10 90 ff 42 08 90 ff
>
> which is enough to identify the oops as in copy_one_pte's get_page(page).
> Here's a patch I think we need, which I'm hoping will fix both your
> crashes - please let us know - thanks a lot.
>
> Stop mprotect's pte_modify from wiping out the x86 pte_special bit, which
> caused oops thereafter when vm_normal_page thought X's abnormal was normal.
[cut patch]
I can report that this fixes things for me as well. Thank you.
next prev parent reply other threads:[~2008-07-06 21:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 6:26 Lockless/Get_User_Pages_Fast causes Xorg 1.4.99.* to lock 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 [this message]
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
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=4871330A.3030400@acm.org \
--to=zlynx@acm.org \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rmh3093@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