linux-kernel - Dropping non supported kernels for kernel backports ?

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-next>] [day] [month] [year] [list]

Message-ID: <CAB=NE6Wy0dp51wDxKzo74Kz=2F-MQjOnARS1r-z3v+LrOwhn-Q@mail.gmail.com>
Date:	Tue, 7 May 2013 16:53:52 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	"backports@...r.kernel.org" <backports@...r.kernel.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Dropping non supported kernels for kernel backports ?

Today the backports project provides support to backport down to
2.6.24 for some subsystems. While this is good for users in practice
for development and maintenance this is quite a bit of overhead. Apart
from older kernels there are also gaps in between stable releases that
are not supported. For example 3.8 and 3.4 are supported but anything
in between is not (3.5, 3.6, 3.7), but we still do support them on the
backports project. At times this may mean a stable fix may get
propagated onto a the linux-3.4.y branch but obviously not the the
linux-3.5.y branch. If backporting expressing this becomes a bit
complex and we have dealt with it. In short, its a pain.

I'd like to see what folks thought if we went ahead and *only*
supported kernels listed on kernel.org as supported. This would help
with the Linux kernel maintainer effort by also persuading users to
upgrade to stable releases as well as educating around this.

If v3.10 backported releases are too soon to do this I propose we
seriously consider it for v3.11 releases. Any thoughts?

  Luis
--
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/