From: Petr Vorel <pvorel@suse.cz>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 3/3] zram/zram03: Convert into new api
Date: Mon, 13 Dec 2021 08:30:03 +0100 [thread overview]
Message-ID: <Ybb2e1QC/HXCsGwV@pevik> (raw)
In-Reply-To: <61B334D8.7000200@fujitsu.com>
Hi all,
> Hi Petr
> > Hi Petr
> >> Hi Xu,
> >>> Also add removing zram module step in setup, so we can avoid the situation that
> >>> zram module is being used by zram-generator.
> >> ...
> >>> +++ b/testcases/kernel/device-drivers/zram/zram03.c
> >> ...
> >>> +static const char *const cmd_rmmod[] = {"rmmod", "zram", NULL};
> >> Again, here should be lsmod used.
> > I prefer to detect it in /proc/modules.
Generally I'd vote for approaches like this to not depend on anything external
to cover more systems (Cyril suggested in v2 SAFE_FOPEN("/proc/modules") and
loop over the lines and do strstr() for zram.)
> > What do you think about it?
> Since we have require modprobe/rmmod commands, using lsmod is better. I
> will use lsmod as you suggested.
OK. I was thinking a bit whether using finit_module would help to replace
modprobe and not require rmmod to cover more systems, but it'd be probably
overcomplicated just for very few systems without kmod installed.
(+ We already depend on all but AOSP on /lib/modules/$(uname
-r)/modules.{dep,builtin} for tst_check_driver().)
Thus ack keeping the current approach.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-12-13 7:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 7:43 [LTP] [PATCH 1/3] swapping01: skip test if zram-swap is being used Yang Xu
2021-12-09 7:43 ` [LTP] [PATCH 2/3] zram/zram_lib.sh: Skip test if zram module can not be removed Yang Xu
2021-12-09 15:17 ` Cyril Hrubis
2021-12-09 21:11 ` Petr Vorel
2021-12-10 8:56 ` xuyang2018.jy
2021-12-10 9:03 ` Petr Vorel
2021-12-10 9:31 ` xuyang2018.jy
2021-12-13 7:40 ` Petr Vorel
2021-12-13 8:05 ` xuyang2018.jy
2021-12-13 10:34 ` Petr Vorel
2021-12-14 3:45 ` xuyang2018.jy
2021-12-14 6:35 ` xuyang2018.jy
2021-12-15 11:56 ` Petr Vorel
2021-12-10 8:27 ` xuyang2018.jy
2021-12-09 7:43 ` [LTP] [PATCH 3/3] zram/zram03: Convert into new api Yang Xu
2021-12-09 21:38 ` Petr Vorel
2021-12-10 10:55 ` xuyang2018.jy
2021-12-10 11:06 ` xuyang2018.jy
2021-12-13 7:30 ` Petr Vorel [this message]
2021-12-10 11:40 ` [LTP] [PATCH v2 1/3] swapping01: skip test if zram-swap is being used Yang Xu
2021-12-10 11:40 ` [LTP] [PATCH v2 2/3] zram/zram_lib.sh: Skip test if zram module can not be removed Yang Xu
2021-12-10 12:25 ` Cyril Hrubis
2021-12-10 11:40 ` [LTP] [PATCH v2 3/3] zram/zram03: Convert into new api Yang Xu
2021-12-10 12:28 ` Cyril Hrubis
2021-12-13 5:44 ` [LTP] [PATCH v3 1/3] swapping01: skip test if zram-swap is being used Yang Xu
2021-12-13 5:44 ` [LTP] [PATCH v3 2/3] zram/zram_lib.sh: Skip test if zram module can not be removed Yang Xu
2021-12-15 6:24 ` xuyang2018.jy
2021-12-10 11:51 ` [LTP] [PATCH v2 1/3] swapping01: skip test if zram-swap is being used Cyril Hrubis
2021-12-10 11:52 ` Cyril Hrubis
2021-12-09 15:15 ` [LTP] [PATCH " Cyril Hrubis
2021-12-09 20:57 ` Petr Vorel
2021-12-10 2:57 ` xuyang2018.jy
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=Ybb2e1QC/HXCsGwV@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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