stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eryu Guan <guaneryu@gmail.com>
Cc: adilger@dilger.ca, ralf@os-t.de, tytso@mit.edu,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "ext4: validate s_first_meta_bg at mount time" has been added to the 3.18-stable tree
Date: Wed, 11 Oct 2017 14:56:21 +0200	[thread overview]
Message-ID: <20171011125621.GF27734@kroah.com> (raw)
In-Reply-To: <20171011040143.GA2503@eguan.usersys.redhat.com>

On Wed, Oct 11, 2017 at 12:01:43PM +0800, Eryu Guan wrote:
> On Tue, Oct 10, 2017 at 08:15:37PM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     ext4: validate s_first_meta_bg at mount time
> > 
> > to the 3.18-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      ext4-validate-s_first_meta_bg-at-mount-time.patch
> > and it can be found in the queue-3.18 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> > 
> > 
> > From 3a4b77cd47bb837b8557595ec7425f281f2ca1fe Mon Sep 17 00:00:00 2001
> > From: Eryu Guan <guaneryu@gmail.com>
> > Date: Thu, 1 Dec 2016 15:08:37 -0500
> > Subject: ext4: validate s_first_meta_bg at mount time
> 
> This patch needs an additional fix, commit 2ba3e6e8afc9 ("ext4: fix
> fencepost in s_first_meta_bg validation"), please make sure it's
> included in the same stable update too.

Ah, good catch, thanks for this, now queued up.

greg k-h

      reply	other threads:[~2017-10-11 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 18:15 Patch "ext4: validate s_first_meta_bg at mount time" has been added to the 3.18-stable tree gregkh
2017-10-11  4:01 ` Eryu Guan
2017-10-11 12:56   ` Greg KH [this message]

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=20171011125621.GF27734@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adilger@dilger.ca \
    --cc=guaneryu@gmail.com \
    --cc=ralf@os-t.de \
    --cc=stable-commits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).