From: Jiri Slaby <jslaby@suse.cz>
To: David Miller <davem@davemloft.net>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
jwboyer@fedoraproject.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: 3.12-stable kernel tree being taken over by Jiri Slaby
Date: Thu, 27 Feb 2014 09:51:21 +0100 [thread overview]
Message-ID: <530EFC89.2010409@suse.cz> (raw)
In-Reply-To: <530EFA78.1020802@suse.cz>
On 02/27/2014 09:42 AM, Jiri Slaby wrote:
> On 02/27/2014 12:39 AM, David Miller wrote:
>> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Date: Wed, 26 Feb 2014 15:19:10 -0800
>>
>>> David, I don't know if you want to keep doing 3.12-networking patches or
>>> not, I'll let you work that out with Jiri directly.
>>
>> 3.12 and 3.13 are very similar, so the work is minimal, therefore I'm
>> likely to keep doing it.
>
> Hi, do you have any plans including:
> commit 18fc25c94eadc52a42c025125af24657a93638c0
> Author: Venkat Venkatsubra <venkat.x.venkatsubra@oracle.com>
> Date: Mon Dec 2 15:41:39 2013 -0800
>
> rds: prevent BUG_ON triggered on congestion update to loopback
>
> which is not needed for 3.13, but is needed for 3.12 to fix CVE-2012-2372?
Nevermind, cherry-pick taught me, that it is already in 3.12.8. We just
have a different fix in the suse tree which should be dropped now.
Sorry for the noise.
--
js
suse labs
next prev parent reply other threads:[~2014-02-27 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 23:19 3.12-stable kernel tree being taken over by Jiri Slaby Greg Kroah-Hartman
2014-02-26 23:39 ` David Miller
2014-02-27 8:42 ` Jiri Slaby
2014-02-27 8:51 ` Jiri Slaby [this message]
2014-02-27 17:55 ` David Miller
2014-02-28 3:02 ` Guenter Roeck
2014-03-01 9:28 ` Jiri Slaby
2014-03-01 19:05 ` Guenter Roeck
2014-02-28 15:58 ` Shuah Khan
2014-03-01 19:53 ` Jiri Slaby
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=530EFC89.2010409@suse.cz \
--to=jslaby@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).