mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH stable-5.4.y] btrfs: fix race between marking inode needs to be logged and log syncing
Date: Mon, 30 Aug 2021 05:28:57 +0800	[thread overview]
Message-ID: <3b67845a-9d24-95d8-9dcf-845df319c0a6@oracle.com> (raw)
In-Reply-To: <YSsvSQR0qHhLeI6C@kroah.com>

On 29/08/2021 14:55, Greg KH wrote:
> On Sat, Aug 28, 2021 at 06:37:28AM +0800, Anand Jain wrote:
>> From: Filipe Manana <fdmanana@suse.com>
>>
>> commit bc0939fcfab0d7efb2ed12896b1af3d819954a14 upstream.
> 
> 5.10 also needs this, can you provide a working backport for that as
> well so that no one would get a regression if they moved to a newer
> kernel release?  Then we could take this patch.

Ok, will do. Why are we keen on stable-5.10.y only, while there are
other stable releases in between?

I just found that this patch applies conflict-free for the stable-5.4.y
to stable-5.8.y, you may consider integrating.

I will send a separate backport for stable-5.10.y.

Thanks, Anand

> 
> thanks,
> 
> greg k-h
> 


  reply	other threads:[~2021-08-29 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 22:37 Anand Jain
2021-08-29  6:55 ` Greg KH
2021-08-29 21:28   ` Anand Jain [this message]
2021-08-30  5:55     ` Greg KH
2021-08-30  6:22       ` Anand Jain
2021-08-29 21:42 ` [PATCH stable-5.9.y, stable-5.10.y] " Anand Jain
2021-09-01  8:14   ` 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=3b67845a-9d24-95d8-9dcf-845df319c0a6@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fdmanana@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®