From: Kurt Kanzenbach <kurt@linutronix.de>
To: Kohei Enju <enjuk@amazon.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kohei.enju@gmail.com, Kohei Enju <enjuk@amazon.com>
Subject: Re: [PATCH v1 iwl-net] igc: unregister netdev when igc_led_setup() fails in igc_probe()
Date: Mon, 08 Sep 2025 08:26:10 +0200 [thread overview]
Message-ID: <87ikht794t.fsf@jax.kurt.home> (raw)
In-Reply-To: <20250906055239.29396-1-enjuk@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
On Sat Sep 06 2025, Kohei Enju wrote:
> Currently igc_probe() doesn't unregister netdev when igc_led_setup()
> fails, causing BUG_ON() in free_netdev() and then kernel panics. [1]
>
> This behavior can be tested using fault-injection framework. I used the
> failslab feature to test the issue. [2]
>
> Call unregister_netdev() when igc_led_setup() fails to avoid the kernel
> panic.
>
> [1]
> kernel BUG at net/core/dev.c:12047!
> Oops: invalid opcode: 0000 [#1] SMP NOPTI
> CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> RIP: 0010:free_netdev+0x278/0x2b0
> [...]
> Call Trace:
> <TASK>
> igc_probe+0x370/0x910
> local_pci_probe+0x3a/0x80
> pci_device_probe+0xd1/0x200
> [...]
>
> [2]
> #!/bin/bash -ex
>
> FAILSLAB_PATH=/sys/kernel/debug/failslab/
> DEVICE=0000:00:05.0
> START_ADDR=$(grep " igc_led_setup" /proc/kallsyms \
> | awk '{printf("0x%s", $1)}')
> END_ADDR=$(printf "0x%x" $((START_ADDR + 0x100)))
>
> echo $START_ADDR > $FAILSLAB_PATH/require-start
> echo $END_ADDR > $FAILSLAB_PATH/require-end
> echo 1 > $FAILSLAB_PATH/times
> echo 100 > $FAILSLAB_PATH/probability
> echo N > $FAILSLAB_PATH/ignore-gfp-wait
>
> echo $DEVICE > /sys/bus/pci/drivers/igc/bind
>
> Fixes: ea578703b03d ("igc: Add support for LEDs on i225/i226")
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
Reviewed-by: Kurt Kanzenbach <kurt@linutronix.de>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2025-09-08 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 5:51 [PATCH v1 iwl-net] igc: unregister netdev when igc_led_setup() fails in igc_probe() Kohei Enju
2025-09-08 6:26 ` Kurt Kanzenbach [this message]
2025-09-10 7:28 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-09-10 7:52 ` Kohei Enju
2025-09-10 8:57 ` Kurt Kanzenbach
2025-09-10 9:15 ` Kohei Enju
2025-09-10 9:02 ` Loktionov, Aleksandr
2025-09-10 9:25 ` Kohei Enju
2025-09-08 6:32 ` Loktionov, Aleksandr
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=87ikht794t.fsf@jax.kurt.home \
--to=kurt@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).