[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023103055-saddled-payer-bd26@gregkh>
Date: Mon, 30 Oct 2023 09:58:41 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: ChenXiaoSong <chenxiaosongemail@...mail.com>
Cc: trond.myklebust@...merspace.com, chenxiaosong@...inos.cn,
Anna.Schumaker@...app.com, sashal@...nel.org,
liuzhengyuan@...inos.cn, huangjinhui@...inos.cn,
liuyun01@...inos.cn, huhai@...inos.cn, linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: Question about LTS 4.19 patch "89047634f5ce NFS: Don't interrupt
file writeout due to fatal errors"
On Mon, Oct 30, 2023 at 04:54:02PM +0800, ChenXiaoSong wrote:
> On 2023/10/30 16:43, Greg KH wrote:
> > Try it and see, but note, that came from the 4.19.99 release which was
> > released years ago, are you sure you are using the most recent 4.19.y
> > release?
>
> I use the most recent release 1b540579cf66 Linux 4.19.296.
>
> > If we missed some patches, that should be added on top of the current
> > tree, please let us know the git commit ids of them after you have
> > tested them that they work properly, and we will gladly apply them.
> Merging the entire patchset may not be the best option. Perhaps a better
> choice is to revert this patch. And I would like to see Trond's suggestion.
>
If you just revert that one patch, is the issue resolved? And what
about other stable releases that have that change in it?
If this does need to be reverted, please submit a patch that does so and
we can review it that way.
thanks,
greg k-h
Powered by blists - more mailing lists