From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Adrian Bunk <bunk@kernel.org>,
DRI <dri-devel@lists.sourceforge.net>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Kumar Gala <galak@kernel.crashing.org>,
Natalie Protasevich <protasnb@gmail.com>,
Martin Bammer <mrb74@gmx.at>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
Linux PM List <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.30-rc6: Reported regressions from 2.6.29
Date: Mon, 18 May 2009 08:32:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0905180819130.3301@localhost.localdomain> (raw)
In-Reply-To: <20090518151102.GA6241@elte.hu>
On Mon, 18 May 2009, Ingo Molnar wrote:
>
> Btw., why did the patch (and the revert) make any difference to the
> test? Timing differences look improbable.
It's the change from
!signal_group_exit(signal)
to
!sig_kernel_only(signr)
and quite frankly, I still don't see the point.
The comment seems to be wrong too:
If SIGSTOP/SIGKILL originate from a descendant of container-init they are
never queued (i.e dropped in sig_ignored() in an earler patch).
If SIGSTOP/SIGKILL originate from parent namespace, the signal is queued
and container-init processes the signal.
since the bug was that the SIGSTOP (from within the same container) was
_not_ ignored like the comment says.
Linus
next prev parent reply other threads:[~2009-05-18 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <_AjETDMbIoL.A.DcH.RYzDKB@chimera>
2009-05-17 7:33 ` 2.6.30-rc6: Reported regressions from 2.6.29 Ingo Molnar
[not found] ` <20090517073327.GC1583@elte.hu>
2009-05-17 10:34 ` Rafael J. Wysocki
2009-05-18 14:57 ` Oleg Nesterov
2009-05-18 15:11 ` Ingo Molnar
2009-05-18 15:31 ` Oleg Nesterov
2009-05-18 15:32 ` Linus Torvalds [this message]
2009-05-18 15:45 ` Oleg Nesterov
2009-05-22 16:40 ` Linus Torvalds
2009-05-23 0:10 ` Rafael J. Wysocki
2009-05-16 19:14 Rafael J. Wysocki
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=alpine.LFD.2.01.0905180819130.3301@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.sourceforge.net \
--cc=galak@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mrb74@gmx.at \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=protasnb@gmail.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