mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Identify security-related patches
Date: Thu, 02 Sep 2004 22:22:43 +0200	[thread overview]
Message-ID: <87y8jsto8c.fsf@deneb.enyo.de> (raw)
In-Reply-To: <4136C6E1.4090404@bio.ifi.lmu.de> (Frank Steiner's message of "Thu, 02 Sep 2004 09:08:17 +0200")

* Frank Steiner:

> is there an easy way to identify all security-related patches out of the
> mass of patches floating around  on linux.bkbits.net or the kernel bugzilla?
>
> I'm running 2.6.8.1 and would like to keep it as stable as possible, thus,
> only apply security patches. Currently I'm searching for "security" and
> alike on bitkeeper, but there seems to be no consistent marking.

No, there isn't.  You won't see any official kernel.org advisories
that could serve as guide, either.

However, your concentration might be a bit short-sighted.  Issues such
as stability (random crashes under load), data corruption (file
systems are corrupted on unmount) and performance (poor throughtput
with some USB devices) could be as important to your users as security
fixes.  In this area, vendor kernels can serve as a guide, too.

Unfortunately, there is no distributed source code management system
used by all these forks, so relating all those changes appears to be
quite complicated.

      parent reply	other threads:[~2004-09-03  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02  7:08 Frank Steiner
2004-09-02 18:48 ` Chris Wright
2004-09-02 19:12   ` Valdis.Kletnieks
2004-09-02 20:22 ` Florian Weimer [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=87y8jsto8c.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®