[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241022142901.GA13306@ziepe.ca>
Date: Tue, 22 Oct 2024 11:29:01 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: syzbot <syzbot+6dee15fdb0606ef7b6ba@...kaller.appspotmail.com>
Cc: leon@...nel.org, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [rdma?] INFO: task hung in add_one_compat_dev (3)
On Tue, Oct 22, 2024 at 12:39:27AM -0700, syzbot wrote:
> 1 lock held by syz-executor/27959:
> #0: ffffffff8fcbffc8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:79 [inline]
> #0: ffffffff8fcbffc8 (rtnl_mutex){+.+.}-{3:3}, at: __rtnl_newlink net/core/rtnetlink.c:3749 [inline]
> #0: ffffffff8fcbffc8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_newlink+0xab7/0x20a0 net/core/rtnetlink.c:3772
There is really something wrong with the new sykzaller reporting, can
someone fix it?
The kernel log that shows the programs:
https://syzkaller.appspot.com/x/log.txt?x=10d72727980000
Doesn't have the word "newlink"/"new"/"link" etc, and yet there is an
executor clearly sitting in a newlink netlink callback when we
crashed.
We need to see the syzkaller programs that are triggering these issues
to get ideas, and for some reason they are missing now.
Jason
Powered by blists - more mailing lists