From: Rik van Riel <riel@redhat.com>
To: Manfred Spraul <manfred@colorfullife.com>,
Davidlohr Bueso <dave@stgolabs.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Rafael Aquini <aquini@redhat.com>
Subject: Re: [PATCH] ipc,sem block sem_lock on sma->lock during sma initialization
Date: Sat, 22 Nov 2014 10:53:20 -0500 [thread overview]
Message-ID: <5470B170.90007@redhat.com> (raw)
In-Reply-To: <54709601.9040606@colorfullife.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/22/2014 08:56 AM, Manfred Spraul wrote:
> Hi Rik,
>
> good catch - I completely forgot to check the initialization
>
> On 11/22/2014 04:40 AM, Rik van Riel wrote:
>>
>> newary initializes a bunch of things after the call to ipc_addid,
>> however some things are initialized inside ipc_addid as well
>>
>> Looking closer at newary, I suppose that it should be possible to
>> move those other initializations before the call to ipc_addid.
>> That would likely get rid of the problem, too.
>>
>> However, I also see this line in newary, and I have no idea what
>> protects that data:
>>
>> ns->used_sems += nsems;
> It should be sem_ids.rwsem, and at least according to the
> documentation both freeary() and newary() hold it.
You're right, that is properly protected already.
- --
All rights reversed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUcLFwAAoJEM553pKExN6DoGwIAJVr0SJWq1sxkRr6quw03OlU
8GUNm8Mz4tVpt1PYSe5r3SIGeT0btEhXjRrqp3IOw7z85Iw5Ed2CwzuLS3aunmpg
hZag9qyArxKBQkbnhtqiM/0AEHbRiju3+sFNC1cQxsdRvLV6QkRveoP5kKvv4v6d
PCMJBHuxL01tPXe5eQC2WjLmI2YPgWWh3fXhDcLt2XTVBI0vwyBiVFc/CtSPERo0
sBF01l/l5KRfOAHduW2kj7KrSF004IgLU7KN5fLG0BzvwlowcHjXgzX7mMCbZrm2
8d8bdEtRJxDZqs4Z9XjDrjXfSdWH/H/5CnfAmvgXA4pswb1lLDLPFbgmt7NUtxk=
=vUfd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-11-22 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 19:52 [PATCH] ipc,sem block sem_lock on sma->lock during sma initialization 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 [this message]
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
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=5470B170.90007@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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 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.