From: Greg KH <gregkh@linuxfoundation.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
"HUANG Weller (CM/ESW12-CN)" <Weller.Huang@cn.bosch.com>,
"George G. Davis" <george_davis@mentor.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Behme Dirk (CM/ESO2)" <Dirk.Behme@de.bosch.com>,
linux-ext4@vger.kernel.org
Subject: Re: Ext4 support for LTS kernels (was: Re: [PATCH 3.14] ext4: fix data exposure after a crash)
Date: Tue, 10 Oct 2017 20:17:10 +0200 [thread overview]
Message-ID: <20171010181710.GL747@kroah.com> (raw)
In-Reply-To: <20171009132004.y6rale4k7oll3hab@thunk.org>
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@vger.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
next prev parent reply other threads:[~2017-10-10 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 21:46 FAILED: patch "[PATCH] ext4: fix data exposure after a crash" failed to apply to 3.14-stable tree gregkh
2016-06-06 0:02 ` HUANG Weller (CM/ESW12-CN)
2016-06-06 0:02 ` HUANG Weller (CM/ESW12-CN)
2016-06-06 5:16 ` Arend van Spriel
2016-06-06 6:17 ` HUANG Weller (CM/ESW12-CN)
2016-06-06 6:17 ` HUANG Weller (CM/ESW12-CN)
2016-06-28 22:31 ` [PATCH 3.14] ext4: fix data exposure after a crash George G. Davis
2016-06-29 7:46 ` Jan Kara
2017-10-06 10:04 ` HUANG Weller (CM/ESW12-CN)
2017-10-09 11:05 ` Jan Kara
2017-10-09 13:20 ` Ext4 support for LTS kernels (was: Re: [PATCH 3.14] ext4: fix data exposure after a crash) Theodore Ts'o
2017-10-10 18:17 ` Greg KH [this message]
2017-10-19 11:35 ` Greg KH
2016-08-14 14:50 ` [PATCH 3.14] ext4: fix data exposure after a crash Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171010181710.GL747@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Dirk.Behme@de.bosch.com \
--cc=Weller.Huang@cn.bosch.com \
--cc=george_davis@mentor.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.