From: Hugh Dickins <hughd@google.com>
To: Louis Alex Eisner <leisner@cs.ucsd.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@kernel.dk>,
linux-mm@kvack.org, Carsten Otte <cotte@de.ibm.com>
Subject: Re: kernel bug: mmap, XIP, page faults, multiple threads
Date: Fri, 27 Jan 2012 19:32:49 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1201271837350.3731@eggly.anvils> (raw)
In-Reply-To: <CAEMjCzJ0JD58xrtPD6DZQbBTwLwcfUphRi+vFUn=nu69s8zH9Q@mail.gmail.com>
On Thu, 26 Jan 2012, Louis Alex Eisner wrote:
>
> I hope I'm sending this to the right people, but I wasn't sure who to
> send it to, since I'm not entirely sure exactly where the bug lives.
> Without further ado:
>
> Summary:
> When multiple threads simultaneously attempt to write to the same page of a
> file which has been mmapped using XIP for the first time, an unhandled
> EBUSY signal causes the kernel to panic.
Thanks a lot for your report, and all the info you carefully gathered.
I confess that I haven't looked at it at all! Because I was thinking
maybe I should take a look, and when did we last hear from Carsten?
And though I now see more recent postings from him in other fields,
what came first to my eye was this nugget below.
It was white-space-damaged and wouldn't apply (I bet that's why it
got lost), so I've fixed that up and reformatted the description,
and added you as a Reporter - but otherwise it's as Carsten posted.
Hugh
prev parent reply other threads:[~2012-01-28 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 3:15 Louis Alex Eisner
2012-01-28 3:32 ` Hugh Dickins [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=alpine.LSU.2.00.1201271837350.3731@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=cotte@de.ibm.com \
--cc=leisner@cs.ucsd.edu \
--cc=linux-mm@kvack.org \
--cc=npiggin@kernel.dk \
/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