From: syzbot <syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com>
To: io-uring@vger.kernel.org, kees@kernel.org, kusaram@devineni.in,
linux-kernel@vger.kernel.org, luto@amacapital.net,
oleg@redhat.com, syzkaller-bugs@googlegroups.com,
wad@chromium.org
Subject: Re: [syzbot] [kernel] WARNING in __secure_computing
Date: Sat, 04 Apr 2026 07:41:01 -0700 [thread overview]
Message-ID: <69d122fd.050a0220.2dbe29.001c.GAE@google.com> (raw)
In-Reply-To: <adEeFek83DrfiJOa@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com
Tested-by: syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com
Tested on:
commit: 7ca6d1cf Merge tag 'powerpc-7.0-4' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=106df3d6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4f34697150c7a709
dashboard link: https://syzkaller.appspot.com/bug?extid=0a4c46806941297fecb9
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=12f9946a580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-04-04 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 4:00 [syzbot] [io-uring?] WARNING in __secure_computing syzbot
2026-02-18 16:27 ` Jens Axboe
2026-02-19 18:53 ` Kees Cook
2026-02-20 13:44 ` Jens Axboe
2026-02-23 19:15 ` Jens Axboe
2026-02-24 0:08 ` Kees Cook
2026-04-04 14:20 ` Oleg Nesterov
2026-04-04 14:41 ` syzbot [this message]
2026-04-05 14:20 ` Oleg Nesterov
2026-04-05 14:40 ` [syzbot] [kernel] " syzbot
2026-04-05 15:10 ` Oleg Nesterov
2026-04-05 15:29 ` 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=69d122fd.050a0220.2dbe29.001c.GAE@google.com \
--to=syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com \
--cc=io-uring@vger.kernel.org \
--cc=kees@kernel.org \
--cc=kusaram@devineni.in \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wad@chromium.org \
/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