linux-kernel - Re: Linux 2.6.16.30-pre1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 24 Sep 2006 21:46:17 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Willy Tarreau <w@....eu>, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.16.30-pre1

Adrian Bunk wrote:
> But having:
> - two saa7134 cards in your computer and
> - one of them formerly not supported and
> - depending on one of them being the first one
> is a case you can theoretically construct, but then there's the point 
> that this is highly unlikely,

Yes, this is an unlikely scenario.

> and OTOH the value of the added support is more realistic.

But then I think people don't really expect additional hardware support
from a stable kernel series.

> If I was as extremely regarding regressions as you describe regarding 
> hardware updates, I would also have to reject any bugfixes that are not 
> security fixes since they might cause regressions.
> 
> I do know that the only value of the 2.6.16 tree lies in a lack of 
> regressions and act accordingly, but I'm trying to do this in a 
> pragmatic way.

If there was more manpower, driver updates could be maintained as extra
patchkits separately to the kernel. I know that some people would like
to have exactly this: A minimally updated base plus a choice of specific
driver updates as add-ons.

In fact that's what I do with the IEEE 1394 drivers --- although not
primarily to support this kind of user base but rather to make it easier
to get bugfixes tested by bug reporters. However I can only afford to do
this by an all-or-nothing approach: I put almost _all_ driver changes
into these patchkits. That means full risk of regressions but also
complete feature updates and minimal divergence from mainline. This was
trivial to do so far.
-- 
Stefan Richter
-=====-=-==- =--= ==---
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/