linux-kernel - Re: Reg the next LTS kernel (6.1?)

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

Date:   Fri, 7 Oct 2022 15:50:12 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Carl Dasantas <dasantas2020@...il.com>
Cc:     Greg KH <gregkh@...uxfoundation.org>, kaiwan.billimoria@...il.com,
        linux-kernel@...r.kernel.org
Subject: Re: Reg the next LTS kernel (6.1?)

On Fri, Oct 07, 2022 at 12:07:05PM -0400, Carl Dasantas wrote:
> It's moreso the fact that initial Rust support is being added. Yes I
> know it's just initial support/NVMe drivers.

Care to name a *single* functional kernel feature (whether a device
driver or not) that is dependent on RUST.  Have you tried building the
latest development kernel without rust --- what happens?  (hint: nothing)

> Also, Rust support isn't the only major
> change in 6.1, by the kernel.orgs own site (time permitting) an LTS is
> made if major changes are present.

This is simply not true.  The start of a new LTS kernel has always
been time-based, and there certainly have been attempts to get new
major functionality around this time of year in the hopes that it can
be made avcailable in distro kernels.  Of course, if the functionality
or change is too flaky, it could very well get reverted or the
distributions will simply not enable the feature because it would be a
support nightmare for them.

All of this does not apply for Rust.  Again, take a look at what is
*actually* been included during the current merge window.

Regards,

						- Ted