From: Rafael Aquini <aquini@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Rik van Riel <riel@redhat.com>,
Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
1vier1@web.de
Subject: Re: [PATCH] ipc,sem block sem_lock on sma->lock during sma initialization
Date: Mon, 24 Nov 2014 05:41:16 -0500 [thread overview]
Message-ID: <20141124104115.GA26444@t510.redhat.com> (raw)
In-Reply-To: <1416778611.11084.2.camel@linux-t7sj.site>
On Sun, Nov 23, 2014 at 01:36:51PM -0800, Davidlohr Bueso wrote:
> On Sun, 2014-11-23 at 16:03 -0500, Rik van Riel wrote:
> > On 11/23/2014 01:23 PM, Manfred Spraul wrote:
> > > Hi Rik,
> > >
> > > On 11/21/2014 08:52 PM, Rik van Riel wrote:
> > >> When manipulating just one semaphore with semop, sem_lock only
> > >> takes that single semaphore's lock. This creates a problem during
> > >> initialization of the semaphore array, when the data structures
> > >> used by sem_lock have not been set up yet. The sma->lock is
> > >> already held by newary, and we just have to make sure everything
> > >> else waits on that lock during initialization.
> > >>
> > >> Luckily it is easy to make sem_lock wait on the sma->lock, by
> > >> pretending there is a complex operation in progress while the sma
> > >> is being initialized.
> > > That's not sufficient, as sma->sem_nsems is accessed before
> > > calling sem_lock(), both within find_alloc_undo() and within
> > > semtimedop().
> > >
> > > The root problem is that sma->sem_nsems and sma->sem_base are
> > > accessed without any locks, this conflicts with the approach that
> > > sma starts to exist as not yet initialized but locked and is
> > > unlocked after the initialization is completed.
> > >
> > > Attached is an idea. It did pass a few short tests. What do you
> > > think?
> >
> > This was my other idea for fixing the issue; unfortunately
> > I didn't think of it until after I sent the first patch :)
>
> Yep, this is what I was mentioning as well.
>
> > You are right that without that change, we can return the
> > wrong error codes to userspace.
> >
> > I will give the patch a try, though I have so far been unable
> > to reproduce the bug that the customer reported, so I am unlikely
> > to give much in the way of useful testing results...
> >
> > Andrew, feel free to give Manfred's patch my
> >
> > Acked-by: Rik van Riel <riel@redhat.com>
>
> Acked-by: Davidlohr Bueso <dave@stgolabs.net>
>
Acked-by: Rafael Aquini <aquini@redhat.com>
next prev parent reply other threads:[~2014-11-24 10:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 19:52 Rik van Riel
2014-11-21 20:07 ` Rafael Aquini
2014-11-21 20:09 ` Andrew Morton
2014-11-21 20:29 ` Rik van Riel
2014-11-21 20:42 ` Andrew Morton
2014-11-21 23:03 ` Rik van Riel
2014-11-22 0:56 ` Davidlohr Bueso
2014-11-22 3:40 ` Rik van Riel
2014-11-22 13:56 ` Manfred Spraul
2014-11-22 15:53 ` Rik van Riel
2014-11-22 19:14 ` Manfred Spraul
2014-11-22 20:14 ` Rik van Riel
2014-11-23 18:23 ` Manfred Spraul
2014-11-23 21:03 ` Rik van Riel
2014-11-23 21:36 ` Davidlohr Bueso
2014-11-24 10:41 ` Rafael Aquini [this message]
2014-11-24 20:49 ` 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=20141124104115.GA26444@t510.redhat.com \
--to=aquini@redhat.com \
--cc=1vier1@web.de \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=riel@redhat.com \
/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