From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Lin Ma <linma@zju.edu.cn>, Corinna Vinschen <vinschen@redhat.com>
Cc: intel-wired-lan@lists.osuosl.org, regressions@lists.linux.dev
Subject: Re: [Intel-wired-lan] [REGRESSION] Deadlock since commit 6faee3d4ee8b ("igb: Add lock to avoid data race")
Date: Tue, 7 Mar 2023 11:19:18 +0100 [thread overview]
Message-ID: <882d6a36-d3ac-c231-ba02-bc2235984cfd@molgen.mpg.de> (raw)
In-Reply-To: <3ef31c0b-ce40-20d0-7740-5dc0cca278ca@molgen.mpg.de>
[Add Corinna back to Cc:, who was removed by Mozilla Thunderbird because
Reply-To header was set for some reason in the original report.]
Am 07.03.23 um 11:12 schrieb Paul Menzel:
> [Adding regressions@lists.linux.dev]
>
> #regzbot ^introduced: 6faee3d4ee8b
>
> Am 07.03.23 um 10:54 schrieb Corinna Vinschen:
>> Hi,
>>
>>
>> After patch 6faee3d4ee8b ("igb: Add lock to avoid data race"), we see
>> a deadlock scenario when trying to unload the igb module.
>>
>> The reproducer is pretty simple:
>>
>> # echo 2 > /sys/class/net/ens5f2/device/sriov_numvfs
>> # modprobe -r igb
>>
>> The hang is quite thorough, I assume it's suffering a deadlock between
>> the rtnl_lock and the spinlock introduced by 6faee3d4ee8b.
>>
>> Any chance you could have a look?
>>
>>
>> Thanks,
>> Corinna
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-03-07 10:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 9:54 [Intel-wired-lan] Deadlock since commit 6faee3d4ee8b ("igb: Add lock to avoid data race") Corinna Vinschen
2023-03-07 10:12 ` [Intel-wired-lan] [REGRESSION] " Paul Menzel
2023-03-07 10:19 ` Paul Menzel [this message]
2023-03-07 10:36 ` Lin Ma
2023-03-07 12:11 ` Corinna Vinschen
2023-03-07 12:37 ` Lin Ma
2023-03-07 12:55 ` Corinna Vinschen
2023-03-07 11:48 ` Lin Ma
2023-03-07 13:05 ` [Intel-wired-lan] [PATCH] igb: revert rtnl_lock() that causes deadlock Lin Ma
2023-03-07 13:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-07 13:45 ` Corinna Vinschen
2023-03-07 15:29 ` [Intel-wired-lan] [PATCH v2] " Lin Ma
2023-03-07 16:27 ` Corinna Vinschen
2023-03-07 23:22 ` Jacob Keller
2023-03-08 12:04 ` Simon Horman
2023-03-16 9:10 ` Romanowski, Rafal
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=882d6a36-d3ac-c231-ba02-bc2235984cfd@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linma@zju.edu.cn \
--cc=regressions@lists.linux.dev \
--cc=vinschen@redhat.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).