stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Greg KH <greg@kroah.com>,
	LKML <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net
Subject: Re: stable-security kernel updates
Date: Thu, 21 Apr 2016 16:33:25 +0200	[thread overview]
Message-ID: <20160421143325.GC9930@1wt.eu> (raw)
In-Reply-To: <5718E362.5010402@oracle.com>

On Thu, Apr 21, 2016 at 10:27:46AM -0400, Sasha Levin wrote:
> This means that missing CVE fixes are quite common with stable trees?

Until someone reports they are missing :-)

Willy


  reply	other threads:[~2016-04-21 14:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 19:50 stable-security kernel updates Sasha Levin
2016-04-21  6:43 ` Jiri Slaby
2016-04-21  7:11   ` Willy Tarreau
2016-04-21 11:27     ` Sasha Levin
2016-04-21 12:36       ` Greg KH
2016-04-21 14:01         ` Sasha Levin
2016-04-21 14:12           ` Willy Tarreau
2016-04-21 11:11   ` Sasha Levin
2016-04-21 11:59     ` Jiri Slaby
2016-04-21 12:05       ` Jiri Slaby
2016-04-21 12:39         ` Greg KH
2016-04-21 12:50           ` Willy Tarreau
2016-04-21 13:54           ` Sasha Levin
2016-04-21 14:13             ` Jiri Slaby
2016-04-21 14:19               ` Willy Tarreau
2016-04-21 14:27               ` Sasha Levin
2016-04-21 14:33                 ` Willy Tarreau [this message]
2016-04-25 23:14                   ` Ben Hutchings
2016-04-26  4:40                     ` Willy Tarreau
2016-04-21 13:53       ` Sasha Levin
2016-04-21 14:54         ` Jiri Slaby
2016-04-21 15:50           ` Sasha Levin
2016-04-21 19:32           ` Sasha Levin
2016-04-21 12:26     ` Bjørn Mork
2016-04-21 12:56 ` Willy Tarreau
2016-04-21 14:16   ` Sasha Levin

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=20160421143325.GC9930@1wt.eu \
    --to=w@1wt.eu \
    --cc=greg@kroah.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.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).