From: Manfred Spraul <manfred@colorfullife.com>
To: Rafael Aquini <aquini@redhat.com>, Davidlohr Bueso <davidlohr@hp.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Greg Thelen <gthelen@google.com>
Subject: Re: [PATCH v2] ipc: introduce ipc_valid_object() helper to sort out IPC_RMID races
Date: Wed, 18 Dec 2013 20:00:36 +0100 [thread overview]
Message-ID: <52B1F0D4.3040502@colorfullife.com> (raw)
In-Reply-To: <20131218173442.GA16621@localhost.localdomain>
Hi Rafael,
On 12/18/2013 06:34 PM, Rafael Aquini wrote:
> Folks,
>
> Before I re-submit the v3 with the commentary changes requested, I'm pasting
> here what I'm planning to amend to v2 patch:
> ---
> diff --git a/ipc/sem.c b/ipc/sem.c
> index ed0057a..23379b6 100644
> --- a/ipc/sem.c
> +++ b/ipc/sem.c
> @@ -1846,6 +1846,14 @@ SYSCALL_DEFINE4(semtimedop, int, semid, struct sembuf __u
>
> error = -EIDRM;
> locknum = sem_lock(sma, sops, nsops);
> + /*
> + * We eventually might perform the following check in a lockless
> + * fashion here, considering ipc_valid_object() locking constraints.
> + * If nsops == 1 and there's no contention for sem_perm.lock, then
> + * only a per-semaphore lock is held and it's OK to go on the check
> + * below. More details on the fine grained locking scheme entangled
> + * here, and why it's RMID race safe on comments at sem_lock()
> + */
> if (!ipc_valid_object(&sma->sem_perm))
> goto out_unlock_free;
> /*
> diff --git a/ipc/util.h b/ipc/util.h
> index 071ed58..d05b708 100644
> --- a/ipc/util.h
> +++ b/ipc/util.h
> @@ -190,7 +190,8 @@ static inline void ipc_unlock(struct kern_ipc_perm *perm)
> * where the respective ipc_ids.rwsem is not being held down.
> * Checks whether the ipc object is still around or if it's gone already, as
> * ipc_rmid() may have already freed the ID while the ipc lock was spinning.
> - * Needs to be called with kern_ipc_perm.lock held.
> + * Needs to be called with kern_ipc_perm.lock held -- exception made for one
> + * checkpoint case at sys_semtimedop() as noted in code commentary.
> */
> static inline bool ipc_valid_object(struct kern_ipc_perm *perm)
> {
> ---
>
> Do we need to change somthing else?
> Looking forward your thoughts!
Acked-by: Manfred Spraul <manfred@colorfullife.com>
--
Manfred
next prev parent reply other threads:[~2013-12-18 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 19:03 [PATCH] ipc: introduce ipc_valid_object() helper to sort out IPC_RMID races Rafael Aquini
2013-12-17 19:31 ` Rik van Riel
2013-12-17 20:41 ` Greg Thelen
2013-12-17 21:27 ` Davidlohr Bueso
2013-12-17 21:46 ` Rafael Aquini
2013-12-17 22:18 ` Davidlohr Bueso
2013-12-17 22:50 ` Rafael Aquini
2013-12-17 23:28 ` [PATCH v2] " Rafael Aquini
2013-12-18 12:11 ` Manfred Spraul
2013-12-18 12:51 ` Rafael Aquini
2013-12-18 13:12 ` Rafael Aquini
2013-12-18 15:46 ` Davidlohr Bueso
2013-12-18 15:53 ` Rafael Aquini
2013-12-18 17:34 ` Rafael Aquini
2013-12-18 19:00 ` Manfred Spraul [this message]
2013-12-18 20:33 ` [PATCH v3] " Rafael Aquini
2013-12-19 0:38 ` Davidlohr Bueso
2013-12-19 0:42 ` Rafael Aquini
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=52B1F0D4.3040502@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=davidlohr@hp.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--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