From: syzbot ci <syzbot+ci3c0828650e63f3bd@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: netdevsim: Fix task hung by releasing bus lock before device ops
Date: Sat, 09 May 2026 03:43:45 -0700 [thread overview]
Message-ID: <69ff0fe1.170a0220.1c0296.020d.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] netdevsim: Fix task hung by releasing bus lock before device ops
https://lore.kernel.org/all/20260509092837.3432281-1-xujiakai24@mails.ucas.ac.cn
* [PATCH] netdevsim: Fix task hung by releasing bus lock before device ops
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/8033a745-648c-476e-90f6-28ef2a0b8b0f
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 8b2feced65cd3aa0597d596ed5733a1abd4c4d78
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/7deaab21-f3c3-4142-afee-11526881734f/config
drivers/net/netdevsim/bus.c:192:3: error: call to undeclared function 'nsim_bus_dev_del'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/net/netdevsim/bus.c:206:13: error: conflicting types for 'nsim_bus_dev_del'
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[davem@davemloft.net edumazet@google.com kuba@kernel.org linux-kernel@vger.kernel.org netdev@vger.kernel.org pabeni@redhat.com xujiakai24@mails.ucas.ac.cn]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-05-09 10:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69ff0fe1.170a0220.1c0296.020d.GAE@google.com \
--to=syzbot+ci3c0828650e63f3bd@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.