mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: syzbot <syzbot+6dee15fdb0606ef7b6ba@syzkaller.appspotmail.com>
Cc: leon@kernel.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	nogikh@google.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [rdma?] INFO: task hung in add_one_compat_dev (3)
Date: Mon, 10 Aug 2026 21:06:41 -0300	[thread overview]
Message-ID: <20260811000641.GA541676@ziepe.ca> (raw)
In-Reply-To: <6a75e1ad.b50370da.49fe0.001b.GAE@google.com>

On Fri, Aug 07, 2026 at 06:46:21AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    f9a2394a2348 Merge tag 'mm-hotfixes-stable-2026-08-06-18-4..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13d50fb9580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8e21dcbdb02d4229
> dashboard link: https://syzkaller.appspot.com/bug?extid=6dee15fdb0606ef7b6ba
> compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14d037b9580000

So this looks like it is just "really slow" beacuse of the vast
amount of work it is triggering in the kernel to manage sysfs files
under locks and the high number of threads running on the same
serializing mutex.

The only way we could do anything about it is to split up the locking
somewhat to be more fine grained, but that seems tricky and
complicated and might trigger a higher level lock anyhow..

I'm not inclined to do that just to silence syzkallers rather
agressive test..

Jason

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22  7:39 syzbot
2024-10-22 14:29 ` Jason Gunthorpe
2024-11-01 15:55   ` Aleksandr Nogikh
2024-11-04 18:14     ` Jason Gunthorpe
2026-08-07 13:46 ` syzbot
2026-08-11  0:06   ` Jason Gunthorpe [this message]

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=20260811000641.GA541676@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=syzbot+6dee15fdb0606ef7b6ba@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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

all inboxes | Powered by JetHome®