Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.vnet.ibm.com>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
	mpm@selenic.com, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH] hw_random: core: Reset user selected rng by writing "" to rng_current
Date: Mon, 30 Oct 2017 14:28:11 +0100	[thread overview]
Message-ID: <c729bc20-1a98-0120-a20a-7bfd8935103b@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171027170404.21262-1-prasannatsmkumar@gmail.com>

On 10/27/2017 07:04 PM, PrasannaKumar Muralidharan wrote:
> User is able to select a chosen rng by writing its name to rng_current
> but there is no way to reset it without unbinding the rng. Let user
> write "" to rng_current and delesect the chosen rng.
>
> Signed-off-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
> ---
>  drivers/char/hw_random/core.c | 51 +++++++++++++++++++++++++++----------------
>  1 file changed, 32 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
> index 9701ac7..be03024 100644
> --- a/drivers/char/hw_random/core.c
> +++ b/drivers/char/hw_random/core.c
> @@ -292,26 +292,48 @@ static struct miscdevice rng_miscdev = {
>  	.groups		= rng_dev_groups,
>  };
>
> +static int enable_best_rng(void)
> +{
> +	int ret = -ENODEV;
> +
> +	BUG_ON(!mutex_is_locked(&rng_mutex));
> +
> +	/* rng_list is sorted by quality, use the best (=first) one */
> +	if (!list_empty(&rng_list)) {
> +		struct hwrng *new_rng;
> +
> +		new_rng = list_entry(rng_list.next, struct hwrng, list);
> +		ret = ((new_rng == current_rng) ? 0 : set_current_rng(new_rng));
> +		if (!ret)
> +			cur_rng_set_by_user = 0;
> +	}
> +
> +	return ret;
> +}
> +
>  static ssize_t hwrng_attr_current_store(struct device *dev,
>  					struct device_attribute *attr,
>  					const char *buf, size_t len)
>  {
> -	int err;
> +	int err = -ENODEV;
Two lines later err is assigned the return value of mutex_lock_interruptible().
So the -ENODEV value assignment does nothing.
>  	struct hwrng *rng;
>
>  	err = mutex_lock_interruptible(&rng_mutex);
>  	if (err)
>  		return -ERESTARTSYS;
> -	err = -ENODEV;
> -	list_for_each_entry(rng, &rng_list, list) {
> -		if (sysfs_streq(rng->name, buf)) {
> -			err = 0;
> -			cur_rng_set_by_user = 1;
> -			if (rng != current_rng)
> +
> +	if (sysfs_streq(buf, "")) {
> +		err = enable_best_rng();
> +	} else {
> +		list_for_each_entry(rng, &rng_list, list) {
> +			if (sysfs_streq(rng->name, buf)) {
> +				cur_rng_set_by_user = 1;
>  				err = set_current_rng(rng);
> -			break;
> +				break;
> +			}
>  		}
>  	}
> +
>  	mutex_unlock(&rng_mutex);
>
>  	return err ? : len;
> @@ -493,17 +515,8 @@ void hwrng_unregister(struct hwrng *rng)
>  	mutex_lock(&rng_mutex);
>
>  	list_del(&rng->list);
> -	if (current_rng == rng) {
> -		drop_current_rng();
> -		cur_rng_set_by_user = 0;
> -		/* rng_list is sorted by quality, use the best (=first) one */
> -		if (!list_empty(&rng_list)) {
> -			struct hwrng *new_rng;
> -
> -			new_rng = list_entry(rng_list.next, struct hwrng, list);
> -			set_current_rng(new_rng);
> -		}
> -	}
> +	if (current_rng == rng)
> +		enable_best_rng();
>
>  	if (list_empty(&rng_list)) {
>  		mutex_unlock(&rng_mutex);
looks like for me.
reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>

  parent reply	other threads:[~2017-10-30 13:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 17:04 [PATCH] hw_random: core: Reset user selected rng by writing "" to rng_current PrasannaKumar Muralidharan
2017-10-30  8:10 ` Harald Freudenberger
2017-10-30 12:59   ` PrasannaKumar Muralidharan
2017-10-30 13:28 ` Harald Freudenberger [this message]
2017-10-30 13:42   ` PrasannaKumar Muralidharan
2017-11-03 14:28 ` Herbert Xu

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=c729bc20-1a98-0120-a20a-7bfd8935103b@linux.vnet.ibm.com \
    --to=freude@linux.vnet.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=prasannatsmkumar@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