From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>,
Johannes Berg <johannes@sipsolutions.net>,
Borislav Petkov <bp@alien8.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@vger.kernel.org>,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 3.0.92
Date: Tue, 20 Aug 2013 09:43:43 -0700 [thread overview]
Message-ID: <20130820164343.GA3958@kroah.com> (raw)
In-Reply-To: <CA+55aFxrPP8=xPWuRVy0HPyiFkT8Mc03zWGKosg+WrEQfqNDfQ@mail.gmail.com>
On Tue, Aug 20, 2013 at 09:33:30AM -0700, Linus Torvalds wrote:
> On Tue, Aug 20, 2013 at 8:57 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Johannes Berg (1):
> > genetlink: fix family dump race
>
> This one turns out to be buggy, see thread called "3.11-rc6 genetlink
> locking fix offends lockdep".
Yeah, I messed up in keeping it here, I'll go revert it and push out a
new 3.0 release.
> I really think there should be delay before stable picks up stuff from
> mainline, unless it's something particularly critical and
> well-discussed.. Maybe a week or so.
I can do that, it's just hard to tell from my end what is "well
discussed" all the time.
> Now it's both in 3.0 and 3.10, so the revert (unless we find a better
> fix - and the first two patches have already failed) will have to go
> there too.
I thought that there was a fix already for this... Ah, no, that was for
another reported regression in an older 3.10-stable release, my bad.
Johannes, what do you want to do here? Just revert it in Linus's tree
for now, given the late -rc cycle?
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-20 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 15:57 Linux 3.0.92 Greg KH
2013-08-20 15:57 ` Greg KH
2013-08-20 16:33 ` Linus Torvalds
2013-08-20 16:43 ` Greg KH [this message]
2013-08-20 19:36 ` Johannes Berg
2013-08-20 20:00 ` Guenter Roeck
2013-08-20 20:07 ` Johannes Berg
2013-08-20 20:08 ` Linus Torvalds
2013-08-20 20:19 ` Guenter Roeck
2013-08-20 18:52 ` David Miller
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=20130820164343.GA3958@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hughd@google.com \
--cc=johannes@sipsolutions.net \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.