LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: Meelis Roos <mroos@linux.ee>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.38-rc3 regression on parisc: segfaults
Date: Fri, 4 Feb 2011 10:20:05 -0500 [thread overview]
Message-ID: <AANLkTim9oXFf7ksuj9o-g2J4aL4xi-JPH3PsayMayxMt@mail.gmail.com> (raw)
In-Reply-To: <20110204150703.GA9254@hiauly1.hia.nrc.ca>
On Fri, Feb 4, 2011 at 10:07 AM, John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:
> On Fri, 04 Feb 2011, Meelis Roos wrote:
>
>> 2363 clone( <unfinished ...>
>> 2349 <... futex resumed> ) = 1
>> 2363 <... clone resumed> child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x460df4a8) = 2372
>> 2349 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>> 2372 rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTART}, <unfinished ...>
>> 2349 write(1, "\33[56;1H\33[34h\33[?25h", 18 <unfinished ...>
>>
>> Something futex-related. Full log temprarilty available at
>> http://www.cs.ut.ee/~mroos/aptitude-strace.txt
>
> This is possibly the infamous COW bug.
The COW bug that is triggered by a COW from an LWS-CAS? The solution
to which is to use locks around the LWS-CAS even on UP? I'd forgotten
about this issue actually, I should push that patch out to James.
Cheers,
Carlos.
next prev parent reply other threads:[~2011-02-04 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 22:00 Meelis Roos
2011-02-01 22:12 ` James Bottomley
2011-02-03 22:36 ` Meelis Roos
2011-02-01 22:16 ` Carlos O'Donell
2011-02-03 2:24 ` John David Anglin
2011-02-03 7:03 ` Meelis Roos
2011-02-04 10:11 ` Meelis Roos
2011-02-04 15:07 ` John David Anglin
2011-02-04 15:20 ` Carlos O'Donell [this message]
2011-02-04 16:17 ` John David Anglin
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=AANLkTim9oXFf7ksuj9o-g2J4aL4xi-JPH3PsayMayxMt@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
--subject='Re: 2.6.38-rc3 regression on parisc: segfaults' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).