From: Mike Galbraith <efault@gmx.de>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
hhuang@redhat.com
Subject: Re: [PATCH 1/2] ipc/sem.c: Race in sem_lock()
Date: Sun, 15 Sep 2013 08:09:03 +0200 [thread overview]
Message-ID: <1379225343.5545.154.camel@marge.simpson.net> (raw)
In-Reply-To: <1379194496-4642-1-git-send-email-manfred@colorfullife.com>
On Sat, 2013-09-14 at 23:34 +0200, Manfred Spraul wrote:
> The bug is probably also present in 3.10 and 3.11, but for these kernels
> is is probably simpler just to move the test of sma->complex_count after
> the spin_is_locked() test.
IMHO, your 6 patch series should go to stable as well. Scalability is
still BAD without them. Now, you've shown the lock split to be buggy.
Logically, the whole thing should be reverted entirely in stable, or
fixed up properly. Humongous improvements will find their way into
every long term stable kernel on the planet regardless, so..
Stable may as well do the Borg thing, resistance really is futile ;-)
-Mike
next prev parent reply other threads:[~2013-09-15 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 21:34 [PATCH 1/2] ipc/sem.c: Race in sem_lock() Manfred Spraul
2013-09-14 21:34 ` [PATCH 2/2] ipc/sem.c: optimize sem_lock() Manfred Spraul
2013-09-15 6:09 ` Mike Galbraith [this message]
2013-09-15 8:06 ` [PATCH 1/2] ipc/sem.c: Race in sem_lock() Mike Galbraith
2013-09-16 11:03 ` Mike Galbraith
2013-09-15 11:34 ` Manfred Spraul
2013-09-15 19:30 ` Davidlohr Bueso
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=1379225343.5545.154.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=davidlohr.bueso@hp.com \
--cc=hhuang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.