public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
	James Morris <jmorris@namei.org>,
	David Howells <dhowells@redhat.com>,
	Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH] selinux_bprm_committed_creds: use __wake_up_parent()
Date: Sat, 4 Jul 2009 10:14:40 +0200	[thread overview]
Message-ID: <20090704081440.GA3558@redhat.com> (raw)
In-Reply-To: <20090703091100.a9667969.akpm@linux-foundation.org>

On 07/03, Andrew Morton wrote:
>
> On Fri, 3 Jul 2009 11:23:11 +0200 Oleg Nesterov <oleg@redhat.com> wrote:
>
> > (depends on ptrace-__ptrace_detach-do-__wake_up_parent-if-we-reap-the-tracee.patch
> >  which exports __wake_up_parent)
> >
> > Spotted by Valdis.Kletnieks@vt.edu.
> >
> > selinux_bprm_committed_creds() should not play with ->wait_chldexit, now
> > that __wake_up_parent() is exported change the code to use this helper.
>
> That's a bit vague.  Why shouldn't it play with wait_chldexit?  What
> changed to make that wrong?

The code was correct (btw, sorry if my message looked as if it is not).

But we should not play with "internal" structures outside of signal/exit
code. So this change is imho good regardless, __wake_up_parent() should
be used to notify threads sleeping in do_wait().

However, __wake_up_parent() was not exported, that is why _committed_creds()
does wake_up by hand.

> Is this a -mm fix?  If so, which -mm patch introduced the problem?

Yes, my fault.

	do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup.patch

assumes that __wake_up_parent() should be always used.

Oleg.


      reply	other threads:[~2009-07-04  8:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 19:51 mmotm 2009-06-30-12-50 uploaded akpm
2009-06-30 20:15 ` Valdis.Kletnieks
2009-06-30 20:19   ` Randy Dunlap
2009-06-30 20:35     ` Andrew Morton
2009-06-30 20:39       ` Randy Dunlap
2009-06-30 20:27   ` Valdis.Kletnieks
2009-06-30 20:38     ` Andrew Morton
2009-07-01  9:21       ` KOSAKI Motohiro
2009-07-02 13:51       ` Valdis.Kletnieks
2009-06-30 21:49 ` [PATCH mmotm] hwmon: fix lis3-spi for CONFIG_PM=n Randy Dunlap
2009-07-02 19:16 ` mmotm 2009-06-30-12-50 uploaded Valdis.Kletnieks
2009-07-02 19:47   ` Andrew Morton
2009-07-02 20:21     ` Valdis.Kletnieks
2009-07-03 10:25     ` Valdis.Kletnieks
2009-07-03  1:52 ` mmotm 2009-06-30-12-50 dies during early boot Valdis.Kletnieks
2009-07-03  2:20   ` Andrew Morton
2009-07-03  8:20     ` Oleg Nesterov
2009-07-03  9:23       ` [PATCH] selinux_bprm_committed_creds: use __wake_up_parent() Oleg Nesterov
2009-07-03  9:39         ` James Morris
2009-07-03 10:12         ` Valdis.Kletnieks
2009-07-03 10:46           ` Oleg Nesterov
2009-07-03 10:16         ` David Howells
2009-07-03 16:11         ` Andrew Morton
2009-07-04  8:14           ` Oleg Nesterov [this message]

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=20090704081440.GA3558@redhat.com \
    --to=oleg@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@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