From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
dave.anglin@nrc-cnrc.gc.ca, linux-parisc@vger.kernel.org,
kyle@mcmartin.ca, James.Bottomley@hansenpartnership.com
Subject: Re: vfork test case.
Date: Wed, 16 Dec 2009 22:22:19 +0100 [thread overview]
Message-ID: <4B294F8B.1070700@gmx.de> (raw)
In-Reply-To: <20091215222119.E6CD84ED7@hiauly1.hia.nrc.ca>
On 12/15/2009 11:21 PM, John David Anglin wrote:
>> I have constructed a vfork test case which shows some of the problems
>> I have using vfork reliably. This fails every time on my PA8700 system
>> running 2.6.32-rc6. It appears as though r28 (ret0) in the parent is
>> being corrupted.
>
> The test doesn't fail on two of my builds:
> Linux mx3210 2.6.31.7 #5 Wed Dec 9 22:49:53 EST 2009 parisc64
> Linux hiauly6 2.6.31.7 #18 Wed Dec 9 21:34:36 EST 2009 parisc
I did tested your testcase on my c3000 too but it didn't failed for me either.
This was on some 2.6.32-rc candidate.
Helge
next prev parent reply other threads:[~2009-12-16 21:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 21:19 vfork test case Carlos O'Donell
2009-12-15 22:21 ` John David Anglin
2009-12-16 13:24 ` Carlos O'Donell
2009-12-16 21:22 ` Helge Deller [this message]
2009-12-16 21:35 ` John David Anglin
2009-12-17 14:24 ` Carlos O'Donell
2009-12-17 16:45 ` dann frazier
2009-12-17 19:12 ` Helge Deller
2009-12-17 20:39 ` Carlos O'Donell
2009-12-19 20:44 ` Grant Grundler
2009-12-17 21:40 ` Berthold Gunreben
2009-12-17 21:59 ` Carlos O'Donell
2010-06-20 4:28 ` John David Anglin
2010-06-22 15:17 ` Carlos O'Donell
2010-06-22 15:39 ` Carlos O'Donell
2010-06-22 22:50 ` John David Anglin
2010-06-27 15:41 ` Carlos O'Donell
2010-06-22 16:26 ` John David Anglin
2010-06-22 18:34 ` Carlos O'Donell
2010-06-22 18:44 ` John David Anglin
2010-06-22 19:53 ` Carlos O'Donell
2010-06-22 20:20 ` John David Anglin
2010-06-22 21:13 ` Carlos O'Donell
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=4B294F8B.1070700@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox