Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Rénich Bon Ćirić" <renich@woralelandia.com>
Cc: <netdev@vger.kernel.org>, <hramamurthy@google.com>
Subject: Re: [PATCH net/gve] gve: fix early boot deadlock between rtnl_lock and service_task_mutex
Date: Wed, 5 Aug 2026 17:01:39 -0700	[thread overview]
Message-ID: <20260805170139.2ddb6216@kernel.org> (raw)
In-Reply-To: <18c88903de19db1f.df50d089680ca23.c305d6e51002e357@desktop.casa.g02.org>

On Tue, 4 Aug 2026 07:18:21 +0000 Rénich Bon Ćirić wrote:
> We hit a reproducible hard deadlock (AB-BA circular lock inversion) during early boot on EL10 / RHEL 10 kernels when running Google Cloud Platform VMs with the gve driver:
> 
> 1. Thread A (NetworkManager): Holds rtnl_lock during __dev_open -> gve_open -> gve_queues_start -> gve_add_napi, and attempts to acquire service_task_mutex.
> 2. Thread B (gve_service_task worker): Holds service_task_mutex, and calls reset recovery which attempts to acquire rtnl_lock.
> 
> Serial Console Trace:
> "INFO: task NetworkManager:856 is blocked on a mutex likely owned by task NetworkManager:856" at RIP: copy_net_ns+0x1a4 / selinux_netlbl_sk_security_free.

You emailed the upstream Linux list.
If the bug exists in the upstream kernel we will happily review the fix
- please post it to the list.

  reply	other threads:[~2026-08-06  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  7:18 [PATCH net/gve] gve: fix early boot deadlock between rtnl_lock and service_task_mutex Rénich Bon Ćirić
2026-08-06  0:01 ` Jakub Kicinski [this message]
2026-08-06 21:28   ` Harshitha Ramamurthy

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=20260805170139.2ddb6216@kernel.org \
    --to=kuba@kernel.org \
    --cc=hramamurthy@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=renich@woralelandia.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