From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: get_user_pages vs mmap MAP_FIXED bug
Date: Wed, 09 May 2007 10:08:34 +1000 [thread overview]
Message-ID: <46411102.5070301@yahoo.com.au> (raw)
In-Reply-To: <1178667269.7286.44.camel@localhost.localdomain>
Hi Rusty!
Rusty Russell wrote:
> On Tue, 2007-05-08 at 17:41 +1000, Nick Piggin wrote:
>
>>Fancy that! Thanks for catching it Rusty, does the following work for
>>you?
>
>
> Hi Nick,
>
> After 24 hours, it seems to be holding up (the original problem showed
> up in lguest, which uses get_user_pages extensively).
>
> Thanks!
> Rusty.
No, thank _you_ for finding the bug :)
--
SUSE Labs, Novell Inc.
prev parent reply other threads:[~2007-05-09 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 7:01 get_user_pages vs mmap MAP_FIXED bug Rusty Russell
2007-05-07 1:26 ` Rusty Russell
2007-05-07 3:22 ` Andrew Morton
2007-05-08 7:41 ` Nick Piggin
2007-05-08 23:34 ` Rusty Russell
2007-05-09 0:08 ` Nick Piggin [this message]
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=46411102.5070301@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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