[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250703014020.2257-1-hdanton@sina.com>
Date: Thu, 3 Jul 2025 09:40:11 +0800
From: Hillf Danton <hdanton@...a.com>
To: syzbot <syzbot+169de184e9defe7fe709@...kaller.appspotmail.com>
Cc: linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [nfs?] [net?] possible deadlock in rpc_close_pipes
> Date: Wed, 02 Jul 2025 10:41:32 -0700
> syzbot found the following issue on:
>
> HEAD commit: 50c8770a42fa Add linux-next specific files for 20250702
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=162e7982580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=70c16e4e191115d4
> dashboard link: https://syzkaller.appspot.com/bug?extid=169de184e9defe7fe709
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1247d770580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ffe48c580000
#syz test
--- x/net/sunrpc/rpc_pipe.c
+++ y/net/sunrpc/rpc_pipe.c
@@ -175,7 +175,7 @@ rpc_close_pipes(struct dentry *dentry)
int need_release;
LIST_HEAD(free_list);
- inode_lock(inode);
+ inode_lock_nested(inode, 1);
spin_lock(&pipe->lock);
need_release = pipe->nreaders != 0 || pipe->nwriters != 0;
pipe->nreaders = 0;
--
Powered by blists - more mailing lists