From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] read_all_sys: skip debugfs
Date: Mon, 4 Nov 2019 11:06:23 -0500 (EST) [thread overview]
Message-ID: <533980280.10363747.1572883583198.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191104155900.GA5683@rei.lan>
----- Original Message -----
> Hi!
> > debugfs is meant for debugging, it exposes also device registers
> > and can pretty much do anything:
> > https://lore.kernel.org/linux-arm-kernel/1507592549.3785589.1570404050459.JavaMail.zimbra@redhat.com/
> > https://lore.kernel.org/stable/2029139028.10333037.1572874551626.JavaMail.zimbra@redhat.com/
> >
> > Signed-off-by: Jan Stancek <jstancek@redhat.com>
> > ---
> > runtest/fs | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/runtest/fs b/runtest/fs
> > index 07d6e2b67964..fba19cae03e8 100644
> > --- a/runtest/fs
> > +++ b/runtest/fs
> > @@ -71,7 +71,7 @@ proc01 proc01 -m 128
> >
> > read_all_dev read_all -d /dev -p -q -r 10
> > read_all_proc read_all -d /proc -q -r 10
> > -read_all_sys read_all -d /sys -q -r 10 -e /sys/power/wakeup_count
> > +read_all_sys read_all -d /sys -q -r 10 -e /sys/power/wakeup_count -e
> > '/sys/kernel/debug/*'
>
> Do we even support multiple parameters for the same option?
>
> I looked that the library code and I would say that we will replace the
> value with each iteration which means that we will effectively use the
> last one.
That is good point. Do we actually need to store blacklist as cmdline parameters?
next prev parent reply other threads:[~2019-11-04 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 15:36 [LTP] [PATCH] read_all_sys: skip debugfs Jan Stancek
2019-11-04 15:59 ` Cyril Hrubis
2019-11-04 16:06 ` Jan Stancek [this message]
2019-11-04 16:10 ` Cyril Hrubis
2019-11-04 16:09 ` Cyril Hrubis
2019-11-04 17:13 ` Jan Stancek
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=533980280.10363747.1572883583198.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.