linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: Wirz <spam@lukas-wirz.de>
Cc: b43-dev@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: b43 crashes on rmmod (bcm4331)
Date: Mon, 11 Jun 2018 22:46:34 +0200	[thread overview]
Message-ID: <20180611224634.28ccd288@wiggum> (raw)
In-Reply-To: <e72be8db-77ba-408c-c5e5-351d722e09e8@lukas-wirz.de>

[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]

On Mon, 11 Jun 2018 23:09:06 +0300
Wirz <spam@lukas-wirz.de> wrote:

> the bisection leads to
> 
> 142a27f0a731ddcf467546960a5585970ca98e21 is the first bad commit
> commit 142a27f0a731ddcf467546960a5585970ca98e21
> Author: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
> Date:   Fri Oct 27 22:34:04 2017 +0530
> 
>     hwrng: core - Reset user selected rng by writing "" to rng_current
> 
>     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>
>     reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
>     Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> 
> :040000 040000 f61e5cc501c99fb09bae5f203528b9f4c3479f8a
> 785262813cfb02c9606fd72274f0f7b44f2289d7 M	drivers


Thanks a lot for bisecting this.

This commit introduces a bug, if b43 is the only RNG in the system. But
that is unlikely on modern systems and it's fixed by
0e4b52942b1c76f89e0dcb829f72e123d0678f54, which is in 4.16.

Other than that I currently can't see why this crashes.

But the crash should go away, if you disable CONFIG_B43_HWRNG.
That's not a solution, but it may help, if you would like to get rid of
the crashes.
Could you please verify whether disabling CONFIG_B43_HWRNG avoids the
crash, just to make sure we are not after a red herring here?

Thanks.

-- 
Michael

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-06-11 20:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 19:55 b43 crashes on rmmod (bcm4331) Wirz
2018-06-09 12:08 ` Wirz
2018-06-09 15:11   ` Michael Büsch
2018-06-09 19:46     ` Wirz
2018-06-09 20:01       ` Michael Büsch
2018-06-11 20:09         ` Wirz
2018-06-11 20:46           ` Michael Büsch [this message]
2018-06-13  9:25             ` Wirz
2018-06-13 10:27               ` Michael Büsch
2018-06-13 11:01                 ` Wirz
2018-06-13 11:09                   ` Michael Büsch
2018-06-13 12:01                     ` Michael Büsch
2018-06-13 13:07                       ` Wirz
2018-06-13 13:28                         ` Michael Büsch
2018-06-14  9:47                           ` Wirz
2018-06-14 16:26                             ` Michael Büsch
2018-06-14 19:18                               ` Wirz

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=20180611224634.28ccd288@wiggum \
    --to=m@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=spam@lukas-wirz.de \
    /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;
as well as URLs for NNTP newsgroup(s).