From: Herbert Xu <herbert@gondor.apana.org.au>
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot+c52ab18308964d248092@syzkaller.appspotmail.com,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, olivia@selenic.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] hwrng: core - fix task hung in hwrng_fillfn
Date: Fri, 1 Dec 2023 17:56:59 +0800 [thread overview]
Message-ID: <ZWmt6wrbxN1W+cnv@gondor.apana.org.au> (raw)
In-Reply-To: <tencent_97BC6EC36EF24C91A7E7C6DFD2C106688906@qq.com>
Edward Adam Davis <eadavis@qq.com> wrote:
>
> diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
> index 420f155d251f..7323ddc958ce 100644
> --- a/drivers/char/hw_random/core.c
> +++ b/drivers/char/hw_random/core.c
> @@ -225,17 +225,18 @@ static ssize_t rng_dev_read(struct file *filp, char __user *buf,
> goto out;
> }
>
> - if (mutex_lock_interruptible(&reading_mutex)) {
> - err = -ERESTARTSYS;
> - goto out_put;
> - }
> if (!data_avail) {
> + if (mutex_lock_interruptible(&reading_mutex)) {
> + err = -ERESTARTSYS;
> + goto out_put;
> + }
> bytes_read = rng_get_data(rng, rng_buffer,
> rng_buffer_size(),
> !(filp->f_flags & O_NONBLOCK));
> + mutex_unlock(&reading_mutex);
> if (bytes_read < 0) {
> err = bytes_read;
> - goto out_unlock_reading;
> + goto out_put;
> }
> data_avail = bytes_read;
> }
Does this change anything at all? Please explain why it was holding
this lock for 143 seconds in the first place. If it's doing it in
rng_get_data, then your change has zero effect.
> @@ -501,7 +499,10 @@ static int hwrng_fillfn(void *unused)
> rng = get_current_rng();
> if (IS_ERR(rng) || !rng)
> break;
> - mutex_lock(&reading_mutex);
> + if (mutex_lock_interruptible(&reading_mutex)) {
> + put_rng(rng);
> + return -ERESTARTSYS;
> + }
No this is just the symptom. The real problem is why is the driver
spending 143 seconds in rng_get_data?
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-12-01 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 13:21 [syzbot] [crypto?] INFO: task hung in hwrng_fillfn syzbot
2023-11-26 7:07 ` [PATCH] hwrng: core - fix " Edward Adam Davis
2023-12-01 9:56 ` Herbert Xu [this message]
2023-12-01 11:37 ` Edward Adam Davis
2023-12-01 11:41 ` Herbert Xu
2023-12-01 12:34 ` Edward Adam Davis
2023-12-01 23:38 ` Herbert Xu
2023-12-02 1:01 ` [PATCH] hwrng: core - Fix page fault dead lock on mmap-ed hwrng Herbert Xu
2023-12-12 14:03 ` PrasannaKumar Muralidharan
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=ZWmt6wrbxN1W+cnv@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=syzbot+c52ab18308964d248092@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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