[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b8caab5918d06f436a889bc1dba09686fc0fad5.camel@hammerspace.com>
Date: Mon, 30 Oct 2023 14:56:40 +0000
From: Trond Myklebust <trondmy@...merspace.com>
To: "chenxiaosongemail@...mail.com" <chenxiaosongemail@...mail.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"chenxiaosong@...inos.cn" <chenxiaosong@...inos.cn>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"huangjinhui@...inos.cn" <huangjinhui@...inos.cn>,
"liuzhengyuan@...inos.cn" <liuzhengyuan@...inos.cn>,
"liuyun01@...inos.cn" <liuyun01@...inos.cn>,
"huhai@...inos.cn" <huhai@...inos.cn>,
"sashal@...nel.org" <sashal@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Anna.Schumaker@...app.com" <Anna.Schumaker@...app.com>
Subject: Re: Question about LTS 4.19 patch "89047634f5ce NFS: Don't interrupt
file writeout due to fatal errors"
On Mon, 2023-10-30 at 17:04 +0800, ChenXiaoSong wrote:
> [You don't often get email from chenxiaosongemail@...mail.com. Learn
> why this is important at
> https://aka.ms/LearnAboutSenderIdentification ]
>
> On 2023/10/30 16:58, Greg KH wrote:
> > 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
>
>
> In my opinion, this patch is not for fixing a bug, but is part of a
> refactoring patchset. The 'Fixes:' tag should not be added.
>
>
A refactoring is by definition a change that does not affect code
behaviour. It is obvious that this was never intended to be such a
patch.
The reason that the bug is occurring in 4.19.x, and not in the latest
kernels, is because the former is missing another bugfix (one which
actually is missing a "Fixes:" tag).
Can you therefore please check if applying commit 22876f540bdf ("NFS:
Don't call generic_error_remove_page() while holding locks") fixes the
issue.
Note that the latter patch is needed in any case in order to fix a read
deadlock (as indicated on the label).
Thanks,
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@...merspace.com
Powered by blists - more mailing lists