From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org, Nick Piggin <npiggin@suse.de>,
Matt Mackall <mpm@selenic.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [S+Q 01/16] [PATCH] ipc/sem.c: Bugfix for semop() not reporting successful operation
Date: Wed, 30 Jun 2010 21:38:43 +0200 [thread overview]
Message-ID: <4C2B9D43.4070504@colorfullife.com> (raw)
In-Reply-To: <20100629120857.00f4b42d.akpm@linux-foundation.org>
Hi Andrew,
On 06/29/2010 09:08 PM, Andrew Morton wrote:
> On Tue, 29 Jun 2010 10:42:42 -0500 (CDT)
> Christoph Lameter<cl@linux-foundation.org> wrote:
>
>
>> This is a patch from Manfred. Required to make 2.6.35-rc3 work.
>>
>>
> My current version of the patch is below.
>
> I believe that Luca has still seen problems with this patch applied so
> its current status is "stuck, awaiting developments".
>
> Is that a correct determination?
>
I would propose that you forward a patch to Linus - either the one you
have in your tree or the v2 that I've just posted.
With stock 2.6.35-rc3, my semtimedop() stress tests produces an oops or
an invalid return value (i.e.:semtimedop() returns with "1") within a
fraction of a second.
With either of the patches applied, my test apps show the expected behavior.
--
Manfred
next prev parent reply other threads:[~2010-06-30 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100625212026.810557229@quilx.com>
[not found] ` <20100625212101.622422748@quilx.com>
2010-06-28 16:48 ` Pekka Enberg
2010-06-29 15:42 ` Christoph Lameter
[not found] ` <20100629120857.00f4b42d.akpm@linux-foundation.org>
2010-06-30 19:38 ` Manfred Spraul [this message]
2010-06-30 19:51 ` Andrew Morton
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=4C2B9D43.4070504@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
/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
Powered by JetHome