From: Greg KH <gregkh@suse.de>
To: Roland Dreier <roland@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Julien Tinnes <jln@google.com>,
Klaus Dittrich <kladit@arcor.de>
Subject: Re: [PATCH v2] Relax si_code check in rt_sigqueueinfo and rt_tgsigqueueinfo
Date: Mon, 11 Apr 2011 11:56:25 -0700 [thread overview]
Message-ID: <20110411185625.GA31235@suse.de> (raw)
In-Reply-To: <AANLkTimb+Kdf9KUNpvMA9qOEZWuPFLsLiwwqZB9M+Awn@mail.gmail.com>
On Tue, Mar 29, 2011 at 10:26:55AM -0700, Roland Dreier wrote:
> On Tue, Mar 29, 2011 at 5:19 AM, Oleg Nesterov <oleg@redhat.com> wrote:
> > Thanks, I think -stable needs this patch asap. It turns out 2.6.32.36, 2.6.33.9,
> > 2.6.37.6 and 2.6.38.2 pulled da48524eb20662618854bb3df2db01fc65f3070c.
>
> Agree... the commit in Linus's tree is tagged for stable@.
>
> The only issue I think is that Greg said he's not doing any more
> 2.6.37 releases?
>
> Greg, this bug breaks the glibc test suite so maybe it's worth doing one more
> release?
Hm, I just checked the distros that I know of that are using the .37
kernel and they already have this patch in them, so it's not really
worth it to me to do another spin of the .37-stable tree. Especially as
I'd like to have everyone move on to .38-stable instead.
thanks,
greg k-h
prev parent reply other threads:[~2011-04-11 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 21:13 [PATCH v2] Relax si_code check in rt_sigqueueinfo and rt_tgsigqueueinfo Roland Dreier
2011-03-28 21:24 ` Julien Tinnes
2011-03-29 12:19 ` Oleg Nesterov
2011-03-29 17:26 ` Roland Dreier
2011-04-11 18:56 ` Greg KH [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=20110411185625.GA31235@suse.de \
--to=gregkh@suse.de \
--cc=jln@google.com \
--cc=kladit@arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=roland@kernel.org \
--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