From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roland McGrath <roland@redhat.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Subject: Re: [BUG] ptraced process waiting on syscall may return kernel internal errnos
Date: Thu, 14 Jun 2007 09:18:49 +1000 [thread overview]
Message-ID: <1181776729.14818.350.camel@localhost.localdomain> (raw)
In-Reply-To: <20070613230153.7B3034D059F@magilla.localdomain>
On Wed, 2007-06-13 at 16:01 -0700, Roland McGrath wrote:
>
> > What about something like:
> >
> > do {
> > rm_from_queue_full(&mask, &t->pending);
> > - recalc_sigpending_and_wake(t);
> > t = next_thread(t);
> > } while (t != current);
> > + recalc_sigpending();
>
> There is no need for the +, just the -. The calling thread is the one
> where know there is certainly no perturbation of behavior due to leaving
> TIF_SIGPENDING set rather than clearing it. It's just going to exit the
> syscall and deal with signal state properly on the way out either way.
> Doing recalc_sigpending is an unnecessary optimization of the corner case.
Fair enough. I'll cook a patch for that one when I'm at work.
> > So at the end of the day, easier to test it inside dequeue_signal().
>
> Before completely revamping the whole set of entrypoints to be saner all
> around, yes.
btw, another interesting grep is to see how tweak TIF_SIGPENDING by
hand ... there's some scary bits in the tty code too...
Ben.
next prev parent reply other threads:[~2007-06-13 23:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 5:47 [BUG] ptraced process waiting on syscall may return kernel internal errnos Satoru Takeuchi
2007-06-06 10:59 ` Roland McGrath
2007-06-06 15:35 ` Linus Torvalds
2007-06-06 23:07 ` Paul Mackerras
2007-06-07 3:25 ` Benjamin Herrenschmidt
2007-06-07 3:27 ` Benjamin Herrenschmidt
2007-06-07 11:33 ` Satoru Takeuchi
2007-06-07 15:54 ` Linus Torvalds
2007-06-07 22:24 ` Benjamin Herrenschmidt
2007-06-08 3:18 ` Linus Torvalds
2007-06-08 5:30 ` Benjamin Herrenschmidt
2007-06-11 22:16 ` Benjamin Herrenschmidt
2007-06-08 3:07 ` Satoru Takeuchi
2007-06-13 22:06 ` Roland McGrath
2007-06-07 3:20 ` Benjamin Herrenschmidt
2007-06-13 15:15 ` Oleg Nesterov
2007-06-13 22:36 ` Benjamin Herrenschmidt
2007-06-13 23:01 ` Roland McGrath
2007-06-13 23:18 ` Benjamin Herrenschmidt [this message]
2007-06-14 0:02 ` Roland McGrath
2007-06-13 22:53 ` Roland McGrath
2007-06-14 12:26 ` Rafael J. Wysocki
2007-06-14 12:58 ` Oleg Nesterov
2007-06-14 23:35 ` Rafael J. Wysocki
2007-06-15 11:31 ` Oleg Nesterov
2007-06-15 21:48 ` Rafael J. Wysocki
2007-06-15 0:06 ` Benjamin Herrenschmidt
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=1181776729.14818.350.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=takeuchi_satoru@jp.fujitsu.com \
--cc=torvalds@linux-foundation.org \
/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