LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@tv-sign.ru>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 2/13] signal/timer/event fds v6 - signalfd core ...
Date: Tue, 20 Mar 2007 01:53:05 +0300	[thread overview]
Message-ID: <20070319225305.GA258@tv-sign.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0703191530270.2101@alien.or.mcafeemobile.com>

On 03/19, Davide Libenzi wrote:
>
> On Mon, 19 Mar 2007, Oleg Nesterov wrote:
> 
> > On 03/19, Davide Libenzi wrote:
> > >
> > > On Mon, 19 Mar 2007, Eric W. Biederman wrote:
> > > 
> > > > > +struct signalfd_ctx {
> > > > > +	struct list_head lnk;
> > > > > +	wait_queue_head_t wqh;
> > > > > +	sigset_t sigmask;
> > > > > +	struct task_struct *tsk;
> > > > > +};
> > > > 
> > > > I think you want to use a struct pid *pid instead of a pointer to the
> > > > task struct here.  It is slightly less efficient (one more
> > > > dereference) but it means that we won't pin the task struct in memory
> > > > indefinitely.  Pinning the task_struct like this makes for a very
> > > > interesting way to get around the limits on the number of processes a
> > > > user can have.
> > > 
> > > Hmm, when the task is detached from the sighand, we get a notify, so I 
> > > could do a put from there. This would avoid the extra de-reference. I need 
> > > to verify locking though ...
> > 
> > In that case (if I understand you correctly) we don't need {get,put}_task_struct()
> > at all.
> > 
> > signalfd_deliver(-1) sets ctx->tsk = NULL, signalfd_get_sighand() reads ->tsk
> > under rcu_read_lock(). The code becomes even simpler, we don't need to check
> > list_empty(&ctx->lnk).
> 
> I'd need a get_task_struct in any case in order to safely call 
> unlock_task_sighand(). At that point I'd prefer to just pass through the 
> struct pid*. I'll be posting the new version for review as soon as I 
> complete a few tests ...

No.

First, you don't need to use unlock_task_sighand(), you can just use
spin_unlock_irqrestore(sighand) directly. But this is, I agree, not good.

If signalfd_get_sighand()->lock_task_sighand() succeeds, it is safe to
dereference ctx->tsk. The task can't be freed and ctx->tsk can't be cleared
while we are holding siglock.

However, I was wrong, we still need a re-check after lock_task_sighand().
We should check ctx->tsk != NULL.

Oleg.


  reply	other threads:[~2007-03-19 22:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16  0:22 Davide Libenzi
2007-03-17 21:35 ` Arnd Bergmann
2007-03-17 21:50   ` Arnd Bergmann
2007-03-18  4:56   ` Stephen Rothwell
2007-03-18 20:31   ` Davide Libenzi
2007-03-18 23:45     ` Arnd Bergmann
2007-03-19  0:22       ` Davide Libenzi
2007-03-19 17:20 ` Eric W. Biederman
2007-03-19 18:53   ` Davide Libenzi
2007-03-19 19:08     ` Eric W. Biederman
2007-03-19 19:11       ` Davide Libenzi
2007-03-19 20:36     ` Oleg Nesterov
2007-03-19 22:33       ` Davide Libenzi
2007-03-19 22:53         ` Oleg Nesterov [this message]
2007-03-19 23:28           ` Oleg Nesterov
2007-03-19 23:34             ` Davide Libenzi

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=20070319225305.GA258@tv-sign.ru \
    --to=oleg@tv-sign.ru \
    --cc=akpm@linux-foundation.org \
    --cc=davidel@xmailserver.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [patch 2/13] signal/timer/event fds v6 - signalfd core ...' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).