To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Identify security-related patches
References: <4136C6E1.4090404@bio.ifi.lmu.de>
From: Florian Weimer <fw@deneb.enyo.de>
Date: Thu, 02 Sep 2004 22:22:43 +0200
In-Reply-To: <4136C6E1.4090404@bio.ifi.lmu.de> (Frank Steiner's message of
	"Thu, 02 Sep 2004 09:08:17 +0200")
Message-ID: <87y8jsto8c.fsf@deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1236
Lines: 26

* 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/