public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Erdogan, Tahsin" <trdgn@amazon.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4.19] ext4: eliminate bogus error in ext4_data_block_valid_rcu()
Date: Mon, 5 Jul 2021 09:06:41 +0200	[thread overview]
Message-ID: <YOKvgbouUTXxmMIl@kroah.com> (raw)
In-Reply-To: <1625362509314.54473@amazon.com>

On Sun, Jul 04, 2021 at 01:35:09AM +0000, Erdogan, Tahsin wrote:
> > If I understand the commit description, this patch is only intended
> > for the 4.19 stable kernel.  If this is the case, I'd suggest using
> > the Subject prefix [PATCH 4.19] for future patches.  This is more
> 
> Hi Ted, yes this is only intended for 4.19. Thanks for the tip on subject line,
> I will keep that in mind in the future.
> 
> > if you could indicate whether a similar fix is needed for 4.14, and
> > other older LTS kernels, or whether the only stable backport which had
> > this bug was 4.19.
> 
> I have checked 4.4, 4.9, 4.14, 5.8. They all look fine. I believe this problem
> only affects 4.19.

THanks, now queued up.

greg k-h

      reply	other threads:[~2021-07-05  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 23:05 [PATCH] ext4: eliminate bogus error in ext4_data_block_valid_rcu() Tahsin Erdogan
2021-07-04  0:58 ` Theodore Ts'o
2021-07-04  1:35   ` [PATCH 4.19] " Erdogan, Tahsin
2021-07-05  7:06     ` Greg Kroah-Hartman [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=YOKvgbouUTXxmMIl@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trdgn@amazon.com \
    --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