public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Calum Mackay <calum.mackay@oracle.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Calum Mackay <calum.mackay@oracle.com>,
	Trond Myklebust <trondmy@hammerspace.com>,
	anna@kernel.org,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	kernel-team@fb.com, ltp@lists.linux.it,
	Avinesh Kumar <akumar@suse.de>, NeilBrown <neilb@suse.de>,
	Sherry Yang <sherry.yang@oracle.com>,
	Josef Bacik <josef@toxicpanda.com>
Subject: [LTP] [PATCH 1/1] nfsstat01: Update client RPC calls for kernel 6.9
Date: Tue, 2 Jul 2024 17:54:49 +0100	[thread overview]
Message-ID: <d4b235df-4ee5-4824-9d48-e3b3c1f1f4d1@oracle.com> (raw)

hi Petr,

I noticed your LTP patch [1][2] which adjusts the nfsstat01 test on v6.9 
kernels, to account for Josef's changes [3], which restrict the NFS/RPC 
stats per-namespace.

I see that Josef's changes were backported, as far back as longterm 
v5.4, so your check for kernel version "6.9" in the test may need to be 
adjusted, if LTP is intended to be run on stable kernels?

best wishes,
calum.


[1] https://lore.kernel.org/ltp/20240620111129.594449-1-pvorel@suse.cz/
[2] 
https://patchwork.ozlabs.org/project/ltp/patch/20240620111129.594449-1-pvorel@suse.cz/
[3] 
https://lore.kernel.org/linux-nfs/cover.1708026931.git.josef@toxicpanda.com/

             reply	other threads:[~2024-07-02 16:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 16:54 Calum Mackay [this message]
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
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=d4b235df-4ee5-4824-9d48-e3b3c1f1f4d1@oracle.com \
    --to=calum.mackay@oracle.com \
    --cc=akumar@suse.de \
    --cc=anna@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=pvorel@suse.cz \
    --cc=sherry.yang@oracle.com \
    --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