[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000881e74061e75c047@google.com>
Date: Tue, 30 Jul 2024 05:02:30 -0700
From: syzbot <syzbot+b668da2bc4cb9670bf58@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [net?] possible deadlock in
team_device_event (3)
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.
***
Subject: Re: [syzbot] [net?] possible deadlock in team_device_event (3)
Author: aha310510@...il.com
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
---
drivers/net/team/team_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/team/team_core.c b/drivers/net/team/team_core.c
index ab1935a4aa2c..056889eff6b1 100644
--- a/drivers/net/team/team_core.c
+++ b/drivers/net/team/team_core.c
@@ -2947,7 +2947,7 @@ static void team_port_change_check(struct team_port *port, bool linkup)
{
struct team *team = port->team;
- mutex_lock(&team->lock);
+ mutex_lock_nested(&team->lock, 1);
__team_port_change_check(port, linkup);
mutex_unlock(&team->lock);
}
--
Powered by blists - more mailing lists