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:   Tue, 10 Oct 2017 20:17:10 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Theodore Ts'o <tytso@....edu>
Cc:     Jan Kara <jack@...e.cz>,
        "HUANG Weller (CM/ESW12-CN)" <Weller.Huang@...bosch.com>,
        "George G. Davis" <george_davis@...tor.com>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "Behme Dirk (CM/ESO2)" <Dirk.Behme@...bosch.com>,
        linux-ext4@...r.kernel.org
Subject: Re: Ext4 support for LTS kernels (was: Re: [PATCH 3.14] ext4: fix
 data exposure after a crash)

On Mon, Oct 09, 2017 at 09:20:04AM -0400, Theodore Ts'o wrote:
> On Mon, Oct 09, 2017 at 01:05:37PM +0200, Jan Kara wrote:
> > On Fri 06-10-17 10:04:41, HUANG Weller (CM/ESW12-CN) wrote:
> > > I checked the latest 3.14 source code 3.14.79. I didn't found the below patch.
> > 
> > Well, I'm not sure who runs the 3.14 stable tree (it's not listed at
> > kernel.org). It's up to him to pick up patches...
> 
> The announcement of 3.14's End of Life as a stable kernel series was
> announced in September 2016.  As far as I know, the fact that 3.14 is
> no longer listed on kernel.org means that no one is maintaining 3.14
> after Greg K-H declared it to be EOL'ed.

Yes, 3.14 is dead :)

> On a side note, I just recently finished an effort to update the ext4
> patches for 3.14, 4.1, 4.4, and 4.9.  I've sent those backports and
> cherry pick requests to stable@...r.kernel.org.  For details of my
> work, at:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> 
> There are testing notes in the signed git tags:
> 
> ext4-4.9.54-1
>    - https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/tag/?h=ext4-4.9.54-1
> ext4-4.4.91-1
>    - https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/tag/?h=ext4-4.4.91-1
> ext4-4.1.44-1
>    - https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/tag/?h=ext4-4.1.44-1
> ext4-3.18.74-1
>    - https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/tag/?h=ext4-3.18.74-1
> 
> .... and on a "when Ted has time / interest basis", the ext4-3.18,
> ext4-4.1, ext4-4.4, and ext-4.9 branches in the above repo will be
> updated with a rebase against the latest LTS kernel and whatever
> patches are needed to minimize xfstests failures that haven't yet
> gotten accepted into the LTS kernel versions.

Thanks so much for this work.  I think I've gotten most of these for
4.9, 4.4, and 3.18, I've emailed about the ones that didn't apply.

> Getting changes into android-common and/or various SOC's BSP kernels
> is left as an exercise to the reader.

android-common syncs with the lts stable releases, so they should get
picked up by the SoC BSP kernels that way.  As long as your SoC company
is sane...

thanks,

greg k-h

Powered by blists - more mailing lists