All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Moese <mmoese@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH] Add library support for /proc/sys/kernel/tainted
Date: Tue, 23 Jan 2018 10:16:16 +0100	[thread overview]
Message-ID: <20180123091616.cc4gafw65z7evrb5@linux.suse> (raw)
In-Reply-To: <20180122153942.GA17451@rei>

Hi,

On Mon, Jan 22, 2018 at 04:39:42PM +0100, Cyril Hrubis wrote:

> This patch lacks information on how this API is supposed to be used
> which is quite important for the review. What I mean is that, while
> important, the documentation for the function parameters and return
> values is not enough. What should be included is some sketch code of
> this is supposed to be used from an actual test source.

Agree. I will spend more effort on the documentation before
submitting again.


> These messages should go out via tst_res().
Agreed.

> We have tst_kvercmp() exactly for this purpose, see include/tst_kvercmp.h
Well, I tried to find this. But somehow I failed :) Thanks for pointing 
this out.

 
> > +	return taint_supported;
> > +}
> > +
> > +unsigned int tst_taint_read(void)
> > +{
> > +	int fd;
> > +	unsigned int val;
> > +	char buffer[11];
> > +
> > +	if (taint_supported == -1)
> > +		tst_taint_supported();
> 
> So this will only cause warning to be printed into the stderr, then we
> go ahead and read the file? Shouldn't we just tst_brk(TCONF, "") at this
> point?
> 
> > +	return val;
> > +}
> > +
> > +int tst_taint_check_mask(unsigned int taint, unsigned int mask)
> > +{
> > +	if ((taint & mask) != 0)
> > +		return 1;
> > +	return 0;
> > +}
> 
> Hmm, should this be combined with the read function?
I had this consideration. But maybe someone needs to compare the flags 
for two points in time, and just check if the mask matched the delta. 
In this case, doing a implicit read would not be what the user wants.
On the other hand, when this is not needed, we could save a line.

Thanks,
Michael

-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

      reply	other threads:[~2018-01-23  9:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 13:12 [LTP] [RFC PATCH] Add library support for /proc/sys/kernel/tainted Michael Moese
2018-01-22 15:39 ` Cyril Hrubis
2018-01-23  9:16   ` Michael Moese [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=20180123091616.cc4gafw65z7evrb5@linux.suse \
    --to=mmoese@suse.de \
    --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.