From: syzbot <syzbot+10a41dc44eef71aa9450@syzkaller.appspotmail.com>
To: immersa.bartosz.chronowski@gmail.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [tipc?] BUG: soft lockup in do_sock_setsockopt
Date: Tue, 11 Aug 2026 07:48:02 -0700 [thread overview]
Message-ID: <6a7b3622.ad2713e4.25b586.0022.GAE@google.com> (raw)
In-Reply-To: <5jt4awsffbzwpq2rqzwbcxkmgqie7jrcls6yl6zqnzknmkilh2@23bp3x25nxqx>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+10a41dc44eef71aa9450@syzkaller.appspotmail.com
Tested-by: syzbot+10a41dc44eef71aa9450@syzkaller.appspotmail.com
Tested on:
commit: a13307e9 Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=161d3132580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7ea511081a30ab4a
dashboard link: https://syzkaller.appspot.com/bug?extid=10a41dc44eef71aa9450
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=118e3132580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-08-11 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ob7cvq6bqedi3rsiyjlcivgfj6mxttkrcrwdciny4brsdpm7yv@zvu3gi5n5cuz>
2026-08-10 14:00 ` syzbot
2026-08-11 10:25 ` Bartosz Chronowski
2026-08-11 14:48 ` syzbot [this message]
2026-08-14 13:29 [PATCH] tipc: defer local Nagle backlog xmit from receive path Bartosz Chronowski
2026-08-14 14:00 ` [syzbot] [tipc?] BUG: soft lockup in do_sock_setsockopt syzbot
[not found] <gzke36g4mm6sanr2fsln44fugfypmfmhnzibyws2ponsbjjius@lgai63h6ahli>
2026-08-07 19:26 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 14:23 syzbot
2024-03-23 0:02 ` Hillf Danton
2024-03-23 8:44 ` syzbot
2024-10-03 9:25 ` 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=6a7b3622.ad2713e4.25b586.0022.GAE@google.com \
--to=syzbot+10a41dc44eef71aa9450@syzkaller.appspotmail.com \
--cc=immersa.bartosz.chronowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®