From: Petr Vorel <pvorel@suse.cz>
To: Sebastian Chlad <sebastianchlad@gmail.com>
Cc: Sebastian Chlad <sebastian.chlad@suse.com>,
Martin Doucha <martin.doucha@suse.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] nfs: Adapt the lib to allow to test in 2-host mode
Date: Mon, 23 Feb 2026 13:01:11 +0100 [thread overview]
Message-ID: <20260223120111.GA462451@pevik> (raw)
In-Reply-To: <CAJCsO8eTiS5Z1Upon-gUj6R9f=TW3BJaRqmDwdxEwSMyvnwB1A@mail.gmail.com>
Hi Sebastian,
...
> > ... if you remove exportfs from TST_NEEDS_CMDS you can use the same code
> > for
> > both netns and 2 based setup (tst_rhost_run should work well on netns).
> good point. I have tested v2 which I will send shortly.
+1
> > I was thinking about having a special variable for checking rhost only, but
> > given that tst_test.sh is now also deprecated, we will have to solve this
> > in
> > shell loader.
> I was also thinking about it but in the end I think it could be just yet
> another variable to control the test flow, so one more thing
> to worry about... and as far as I see relying on the presence of already
> defined variables seems good enough.
Until shell loader came I thought we'd parse tests which use tst_test.sh
(I thought therefore these variables would be used in metadata).
Now I'm thinking whether write the minimal tst_net.sh functionality directly in C
as either new library (code in libs/) or just core library extension (lib/*.c).
For sure it'd be quicker just to put subset of required code into new script,
but it's worth to consider it. That would also help rewrite tests in C in the
future.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-02-23 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 13:53 [LTP] [PATCH] nfs: Adapt the lib to allow to test in 2-host mode Sebastian Chlad
2026-02-22 20:34 ` Petr Vorel
2026-02-23 10:41 ` Sebastian Chlad
2026-02-23 10:55 ` [LTP] [PATCH v2] " Sebastian Chlad
2026-02-24 9:24 ` Petr Vorel
2026-02-23 12:01 ` Petr Vorel [this message]
2026-02-23 16:54 ` [LTP] [PATCH] " Cyril Hrubis
2026-02-23 17:01 ` Sebastian Chlad via ltp
2026-02-24 9:38 ` Petr Vorel
2026-02-24 10:44 ` Cyril Hrubis
2026-02-24 11:46 ` Petr Vorel
2026-02-24 12:20 ` Cyril Hrubis
2026-02-24 16:11 ` Petr Vorel
2026-02-25 9:24 ` Sebastian Chlad
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=20260223120111.GA462451@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.com \
--cc=sebastian.chlad@suse.com \
--cc=sebastianchlad@gmail.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