All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Otte <cotte@de.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Hugh Dickins <hugh@veritas.com>,
	benh@kernel.crashing.org, 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, 07 Jul 2008 17:43:58 +0200	[thread overview]
Message-ID: <487239BE.8070505@de.ibm.com> (raw)
In-Reply-To: <200807071806.11630.nickpiggin@yahoo.com.au>

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?
I've done my best to combine mprotect, mmap and munmap a MAP_PRIVATE 
mapping on a xip file system. The system runs stable with and without 
this patch. Could someone please enlighten me on how to reproduce the 
problem so that I can verify the fix?

  parent reply	other threads:[~2008-07-07 15:44 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
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 [this message]
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=487239BE.8070505@de.ibm.com \
    --to=cotte@de.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=carsteno@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.