From: Jonathan Nieder <jrnieder@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net
Subject: Re: Linux 3.2.18
Date: Mon, 21 May 2012 09:27:00 -0500 [thread overview]
Message-ID: <20120521142643.GA28118@burratino> (raw)
In-Reply-To: <CAFLxGvzdyr08UjHy_85CeHV=bB2nzzTy0JOdgLFx6x3mwOasdw@mail.gmail.com>
Hi Richard,
richard -rw- weinberger wrote:
> On Mon, May 21, 2012 at 4:02 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
>> All users of the 3.2 kernel series should upgrade.
>
> Should or must?
Every stable update probably includes some fixes that are
security-relevant for someone. That said, no one on this list has
volunteered to do the nontrivial work of categorizing them (and that
is not the purpose of this list anyway). You're more likely to find
useful information from your distributor or from sources such as the
national vulnerability database.
Amazingly enough, the difference between "should" and "must" is not a
secret message but just a difference in diction between Ben and Greg.
"All users should upgrade" would generally mean that it is prudent for
all users to upgrade, rather than some particular subset of them
(e.g., users who have been experiencing build failures).
Kind regards,
Jonathan
next prev parent reply other threads:[~2012-05-21 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 14:02 Linux 3.2.18 Ben Hutchings
2012-05-21 14:06 ` Ben Hutchings
2012-05-21 14:18 ` richard -rw- weinberger
2012-05-21 14:24 ` Ben Hutchings
2012-05-21 14:30 ` richard -rw- weinberger
2012-05-21 14:27 ` Jonathan Nieder [this message]
2012-05-21 14:27 ` Willy Tarreau
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=20120521142643.GA28118@burratino \
--to=jrnieder@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=richard.weinberger@gmail.com \
--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