From: syzbot <syzbot+e2af46126e0644cbebdd@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, raoxu@uniontech.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] unregister_netdevice: waiting for DEV to become free (9)
Date: Wed, 13 May 2026 18:59:03 -0700 [thread overview]
Message-ID: <6a052c67.170a0220.196691.0002.GAE@google.com> (raw)
In-Reply-To: <B2CF7974DC914535+20260514015049.255578-1-raoxu@uniontech.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
error: corrupt patch at line 24
Tested on:
commit: 59afae20 selftests/tc-testing: Add QFQ/CBS qlen underf..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git main
kernel config: https://syzkaller.appspot.com/x/.config?x=a834c6344141a58b
dashboard link: https://syzkaller.appspot.com/bug?extid=e2af46126e0644cbebdd
compiler:
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=14415636580000
next parent reply other threads:[~2026-05-14 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B2CF7974DC914535+20260514015049.255578-1-raoxu@uniontech.com>
2026-05-14 1:59 ` syzbot [this message]
[not found] <FBE6DA28176D6E90+20260514115843.1655377-1-raoxu@uniontech.com>
2026-05-14 12:28 ` [syzbot] [net?] unregister_netdevice: waiting for DEV to become free (9) syzbot
[not found] <FF91F2BF42AC95B3+20260514111238.1600030-1-raoxu@uniontech.com>
2026-05-14 11:43 ` syzbot
[not found] <BD680186E4DE6711+20260514082426.721996-1-raoxu@uniontech.com>
2026-05-14 9:20 ` syzbot
[not found] <E61E4EBE5175D344+20260514064805.611177-1-raoxu@uniontech.com>
2026-05-14 7:30 ` syzbot
[not found] <113A84FF927506B4+20260514040220.410747-1-raoxu@uniontech.com>
2026-05-14 5:36 ` syzbot
[not found] <0CE6AE93FEBA21AC+20260514023628.308904-1-raoxu@uniontech.com>
2026-05-14 2:45 ` syzbot
[not found] <950831E2452101D8+20260514020809.275684-1-raoxu@uniontech.com>
2026-05-14 2:17 ` syzbot
2026-05-10 20:18 syzbot
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=6a052c67.170a0220.196691.0002.GAE@google.com \
--to=syzbot+e2af46126e0644cbebdd@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raoxu@uniontech.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 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.