From: Bruce Fields <bfields@fieldses.org>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Chuck Lever <chuck.lever@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"940821@bugs.debian.org" <940821@bugs.debian.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
trond.myklebust@hammerspace.com, anna.schumaker@netapp.com
Subject: Re: NFS Caching broken in 4.19.37
Date: Sun, 21 Feb 2021 09:37:12 -0500 [thread overview]
Message-ID: <20210221143712.GA15975@fieldses.org> (raw)
In-Reply-To: <9305dc03-5557-5e18-e5c9-aaf886a03fff@cambridgegreys.com>
On Sun, Feb 21, 2021 at 11:38:51AM +0000, Anton Ivanov wrote:
> On 21/02/2021 09:13, Salvatore Bonaccorso wrote:
> >On Sat, Feb 20, 2021 at 08:16:26PM +0000, Chuck Lever wrote:
> >>Confirming you are varying client-side kernels. Should the Linux
> >>NFS client maintainers be Cc'd?
> >
> >Ok, agreed. Let's add them as well. NFS client maintainers any ideas
> >on how to trackle this?
>
> This is not observed with Debian backports 5.10 package
>
> uname -a
> Linux madding 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1
> (2021-02-11) x86_64 GNU/Linux
I'm still unclear: when you say you tested a certain kernel: are you
varying the client-side kernel version, or the server side, or both at
once?
--b.
next prev parent reply other threads:[~2021-02-21 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 18:19 NFS Caching broken in 4.19.37 Anton Ivanov
2021-02-20 20:04 ` Salvatore Bonaccorso
2021-02-20 20:13 ` Anton Ivanov
2021-02-20 20:16 ` Chuck Lever
2021-02-21 9:13 ` Salvatore Bonaccorso
2021-02-21 11:38 ` Anton Ivanov
2021-02-21 14:37 ` Bruce Fields [this message]
2021-02-21 15:53 ` Anton Ivanov
2021-02-26 15:03 ` Timo Rothenpieler
2021-02-26 15:40 ` Anton Ivanov
2021-02-26 15:48 ` Timo Rothenpieler
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=20210221143712.GA15975@fieldses.org \
--to=bfields@fieldses.org \
--cc=940821@bugs.debian.org \
--cc=anna.schumaker@netapp.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=carnil@debian.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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