From: Cyril Hrubis <chrubis@suse.cz>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Greg KH <greg@kroah.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Neil Brown <neilb@suse.de>, Jeff Layton <jlayton@kernel.org>,
Sherry Yang <sherry.yang@oracle.com>,
linux-stable <stable@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Anna Schumaker <anna@kernel.org>,
Trond Myklebust <trondmy@hammerspace.com>,
Calum Mackay <calum.mackay@oracle.com>,
"kernel-team@fb.com" <kernel-team@fb.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/1] nfsstat01: Update client RPC calls for kernel 6.9
Date: Tue, 9 Jul 2024 08:48:32 +0200 [thread overview]
Message-ID: <ZozdQCwODOyO73U_@rei> (raw)
In-Reply-To: <64D2D29F-BCC0-4A44-BB75-D85B80B75959@oracle.com>
Hi!
> There is a change in behavior in the upstream code, but Josef's
> patches fix an information leak and make the statistics more
> sensible in container environments. I'm not certain that
> should be considered a regression, but confess I don't know
> the regression rules to this fine a degree of detail.
>
> If it is indeed a regression, how can we go about retaining
> both behaviors (selectable by Kconfig or perhaps administrative
> UI)?
That is IMHO the worst solution, every userspace tool would have to be
able to work with both formats for an undefinite amount of time and the
only added value of this approach would be a Kconfig option to enable
information leak...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2024-07-09 6:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4b235df-4ee5-4824-9d48-e3b3c1f1f4d1@oracle.com>
2024-07-02 22:55 ` [LTP] [PATCH 1/1] nfsstat01: Update client RPC calls for kernel 6.9 Calum Mackay
2024-07-05 14:19 ` Chuck Lever III
2024-07-06 7:11 ` Greg KH
2024-07-06 7:46 ` Sherry Yang
2024-07-08 10:36 ` Greg KH
2024-07-08 17:49 ` Chuck Lever III
2024-07-09 6:48 ` Cyril Hrubis [this message]
2024-07-11 21:18 ` Jeff Layton
2024-07-11 22:58 ` NeilBrown
2024-07-12 0:40 ` Jeff Layton
2024-07-12 6:12 ` NeilBrown
2024-07-12 10:16 ` Jeff Layton
2024-07-12 11:07 ` Petr Vorel
2024-07-12 14:03 ` Chuck Lever III
2024-07-12 11:13 ` NeilBrown
2024-08-14 20:55 ` Petr Vorel
2024-08-14 22:17 ` NeilBrown
2024-08-15 6:53 ` Petr Vorel
2024-07-12 13:45 ` Thorsten Leemhuis
2024-07-12 14:07 ` Jeff Layton
2024-07-08 4:02 ` Petr Vorel
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=ZozdQCwODOyO73U_@rei \
--to=chrubis@suse.cz \
--cc=anna@kernel.org \
--cc=calum.mackay@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=greg@kroah.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=neilb@suse.de \
--cc=sherry.yang@oracle.com \
--cc=stable@vger.kernel.org \
--cc=trondmy@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