From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/3] nfs_lib.sh: Add nfs_get_remote_path()
Date: Tue, 23 Nov 2021 20:26:49 +0100 [thread overview]
Message-ID: <YZ1AefvsjpFwsbti@pevik> (raw)
In-Reply-To: <20211123151537.14913-1-mdoucha@suse.cz>
Hi Martin,
> Sometimes it's necessary to manipulate remote NFS directory directly e.g.
> to simulate external server activity. nfs_get_remote_path() will print
> the remote path so that it can then be used by tst_rhost_run().
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
> Signed-off-by: Martin Doucha <mdoucha@suse.cz>
> ---
> Changes since v1: None
> testcases/network/nfs/nfs_stress/nfs_lib.sh | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
> diff --git a/testcases/network/nfs/nfs_stress/nfs_lib.sh b/testcases/network/nfs/nfs_stress/nfs_lib.sh
> index 206f11fdd..790655643 100644
> --- a/testcases/network/nfs/nfs_stress/nfs_lib.sh
> +++ b/testcases/network/nfs/nfs_stress/nfs_lib.sh
> @@ -52,6 +52,19 @@ get_socket_type()
> done
> }
> +nfs_get_remote_path()
> +{
> + local v
> + local type=$(get_socket_type ${2:-0})
> +
> + for v in $VERSION; do
> + break;
> + done
> +
> + v=${1:-$v}
> + echo "$TST_TMPDIR/$v/$type"
> +}
> +
> nfs_server_udp_enabled()
> {
> local config f
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2021-11-23 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 15:15 [LTP] [PATCH v2 1/3] nfs_lib.sh: Add nfs_get_remote_path() Martin Doucha
2021-11-23 15:15 ` [LTP] [PATCH v2 2/3] nfs_lib.sh: Add support for test-specific parameters Martin Doucha
2021-11-23 19:29 ` Petr Vorel
2021-11-23 15:15 ` [LTP] [PATCH v2 3/3] Add test for NFS directory listing regression Martin Doucha
2021-11-23 19:40 ` Petr Vorel
2021-11-24 9:27 ` Martin Doucha
2021-11-24 9:50 ` Petr Vorel
2021-11-24 10:06 ` Martin Doucha
2021-11-24 10:27 ` Petr Vorel
2021-11-24 14:07 ` Alexey Kodanev
2021-11-24 14:12 ` Martin Doucha
2021-11-25 11:06 ` Petr Vorel
2021-11-25 13:27 ` Petr Vorel
2021-11-23 19:26 ` Petr Vorel [this message]
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=YZ1AefvsjpFwsbti@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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