public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
To: akpm@linux-foundation.org, manfred@colorfullife.com,
	herton@redhat.com, penguin-kernel@i-love.sakura.ne.jp,
	rientjes@google.com, dave@stgolabs.net, joe@perches.com,
	linux-kernel@vger.kernel.org
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Subject: [PATCH] Don't set sempid in semctl syscall.
Date: Fri, 26 Feb 2016 17:51:38 +0530	[thread overview]
Message-ID: <1456489298-20224-1-git-send-email-prasannatsmkumar@gmail.com> (raw)

From: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>

As described in bug #112271 (bugzilla.kernel.org/show_bug.cgi?id=112271)
don't set sempid in semctl syscall. Set sempid only when semop is called.

Signed-off-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
---
 ipc/sem.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/ipc/sem.c b/ipc/sem.c
index e626965..4a99220 100644
--- a/ipc/sem.c
+++ b/ipc/sem.c
@@ -1341,7 +1341,6 @@ static int semctl_setval(struct ipc_namespace *ns, int semid, int semnum,
 		un->semadj[semnum] = 0;
 
 	curr->semval = val;
-	curr->sempid = task_tgid_vnr(current);
 	sma->sem_ctime = get_seconds();
 	/* maybe some queued-up processes were waiting for this */
 	do_smart_update(sma, NULL, 0, 0, &tasks);
-- 
2.5.0

             reply	other threads:[~2016-02-26 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 12:21 PrasannaKumar Muralidharan [this message]
2016-02-26 20:19 ` [PATCH] Don't set sempid in semctl syscall Manfred Spraul
2016-02-26 22:15   ` Davidlohr Bueso
2016-02-26 22:18     ` Davidlohr Bueso
2016-02-27  8:42   ` PrasannaKumar Muralidharan
2016-02-28 19:16     ` Michael Kerrisk
2016-02-29 21:22       ` Davidlohr Bueso
2016-03-01  7:48         ` Michael Kerrisk (man-pages)

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=1456489298-20224-1-git-send-email-prasannatsmkumar@gmail.com \
    --to=prasannatsmkumar@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=herton@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=rientjes@google.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