public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 2/2] testcaes/lib: Add shell loader
Date: Thu, 25 Jul 2024 13:02:06 +0200	[thread overview]
Message-ID: <20240725110206.GA982789@pevik> (raw)
In-Reply-To: <d5cb1dc4-7bd7-4084-952d-95511cbbb907@suse.cz>

Hi Martin, Cyril,

> Hi,
> one note below.
...
> > --- /dev/null
> > +++ b/testcases/lib/tests/shell_loader_all_filesystems.sh
> > @@ -0,0 +1,22 @@
> > +#!/bin/sh
> > +#
> > +# needs_root=1
> > +# mount_device=1
> > +# all_filesystems=1
> > +
> > +TST_MNTPOINT=ltp_mntpoint
> > +
> > +. tst_env.sh
> > +
> > +tst_res TINFO "IN shell"
> > +
> > +mounted=$(grep $TST_MNTPOINT /proc/mounts)

> This check might produce false positive for example when another LTP shell
> script runs in parallel in another temp directory. I'd recommend using
> $(realpath ...) to disambiguate the mountpoints.

FYI this is just a test, not a library script.

Also maybe just prepend it with $PWD/ would be enough:

mounted=$(grep $PWD/$TST_MNTPOINT /proc/mounts)

(Not to require yet another binary. It's ok to have it here, because developers
have coreutils, but in case it's in the tst_test.sh or its dependencies some
minimal systems might have problem - busybox based embedded systems realpath is
configurable via CONFIG_REALPATH=y. It would help if we specify shell library
dependencies).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-07-25 11:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 15:36 [LTP] [RFC PATCH 0/2] Shell test library v3 Cyril Hrubis
2024-07-16 15:36 ` [LTP] [RFC PATCH 1/2] Add support for mixing C and shell code Cyril Hrubis
2024-07-17  8:33   ` Li Wang
2024-07-17  8:41     ` Cyril Hrubis
2024-07-17 10:07       ` Li Wang
2024-07-17  8:52     ` Cyril Hrubis
2024-07-17 10:21       ` Li Wang
2024-07-17 17:51         ` Petr Vorel
2024-07-17 17:55         ` Petr Vorel
2024-07-17 18:13           ` Cyril Hrubis
2024-07-18 12:43   ` Petr Vorel
2024-07-18 13:03     ` Cyril Hrubis
2024-07-18 12:57   ` Petr Vorel
2024-07-18 13:07     ` Cyril Hrubis
2024-07-18 13:15       ` Petr Vorel
2024-07-24  9:37   ` Martin Doucha
2024-07-24  9:47     ` Cyril Hrubis
2024-07-24  9:53       ` Martin Doucha
2024-07-24 10:05         ` Cyril Hrubis
2024-07-30  9:49     ` Cyril Hrubis
2024-07-16 15:36 ` [LTP] [RFC PATCH 2/2] testcaes/lib: Add shell loader Cyril Hrubis
2024-07-24 12:54   ` Martin Doucha
2024-07-25 11:02     ` Petr Vorel [this message]
2024-07-25 16:01       ` Martin Doucha
2024-07-25 21:44         ` 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=20240725110206.GA982789@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