From: syzbot <syzbot+984a5c208d87765b2ee7@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mjguzik@gmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] kernel BUG in sctp_getsockopt_peeloff_common
Date: Mon, 01 Dec 2025 05:45:03 -0800 [thread overview]
Message-ID: <692d9bdf.a70a0220.d98e3.018a.GAE@google.com> (raw)
In-Reply-To: <cenhvze4xmjyddtovfr36c767ttt2dgbprtr4zef6n7wrkgrze@mnzax7kfeegk>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+984a5c208d87765b2ee7@syzkaller.appspotmail.com
Tested-by: syzbot+984a5c208d87765b2ee7@syzkaller.appspotmail.com
Tested on:
commit: 95cb2fd6 Add linux-next specific files for 20251201
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=142b58c2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=caadf525b0ab8d17
dashboard link: https://syzkaller.appspot.com/bug?extid=984a5c208d87765b2ee7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=10a62512580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-12-01 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:58 [syzbot] [fs?] kernel BUG in sctp_getsockopt_peeloff_common syzbot
2025-12-01 12:57 ` Mateusz Guzik
2025-12-01 13:45 ` syzbot [this message]
2025-12-01 14:07 ` Al Viro
2025-12-02 9:49 ` Christian Brauner
2025-12-01 22:09 ` syzbot
2025-12-04 22:53 ` Xin Long
2025-12-05 9:44 ` Christian Brauner
2025-12-25 14:39 ` Tetsuo Handa
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=692d9bdf.a70a0220.d98e3.018a.GAE@google.com \
--to=syzbot+984a5c208d87765b2ee7@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.