mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ChenXiaoSong <chenxiaosongemail@foxmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: trond.myklebust@hammerspace.com, chenxiaosong@kylinos.cn,
	Anna.Schumaker@netapp.com, sashal@kernel.org,
	liuzhengyuan@kylinos.cn, huangjinhui@kylinos.cn,
	liuyun01@kylinos.cn, huhai@kylinos.cn, linux-nfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Question about LTS 4.19 patch "89047634f5ce NFS: Don't interrupt file writeout due to fatal errors"
Date: Mon, 30 Oct 2023 16:54:02 +0800	[thread overview]
Message-ID: <tencent_4CA081DD6E435CDA2EAB9C826F7899F78C05@qq.com> (raw)
In-Reply-To: <2023103055-anaerobic-childhood-c1f1@gregkh>

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.


  reply	other threads:[~2023-10-30  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  8:39 ChenXiaoSong
2023-10-30  8:43 ` Greg KH
2023-10-30  8:54   ` ChenXiaoSong [this message]
2023-10-30  8:58     ` Greg KH
2023-10-30  9:04       ` ChenXiaoSong
2023-10-30  9:19         ` Greg KH
2023-10-30 14:56         ` Trond Myklebust
2023-11-17  3:28           ` ChenXiaoSong
2023-11-17  4:09           ` ChenXiaoSong

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=tencent_4CA081DD6E435CDA2EAB9C826F7899F78C05@qq.com \
    --to=chenxiaosongemail@foxmail.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=chenxiaosong@kylinos.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=huangjinhui@kylinos.cn \
    --cc=huhai@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=liuyun01@kylinos.cn \
    --cc=liuzhengyuan@kylinos.cn \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.com \
    /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®