From: syzbot <syzbot+cb76c2983557a07cdb14@syzkaller.appspotmail.com>
To: keescook@chromium.org, linux-kernel@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [arm] BUG: bad usercopy in fpa_set
Date: Fri, 05 Apr 2024 07:25:03 -0700 [thread overview]
Message-ID: <000000000000c5572506155a38b8@google.com> (raw)
In-Reply-To: <cb6d724f-7afb-44c6-835c-6c8c229b70a0@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+cb76c2983557a07cdb14@syzkaller.appspotmail.com
Tested on:
commit: 8cb4a9a8 x86/cpufeatures: Add CPUID_LNX_5 to track rec..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d6c52d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=39e01873cab062c1
dashboard link: https://syzkaller.appspot.com/bug?extid=cb76c2983557a07cdb14
compiler: arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm
patch: https://syzkaller.appspot.com/x/patch.diff?x=14c42099180000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-04-05 14:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 12:53 [syzbot] [hardening?] [mm?] BUG: bad usercopy in fpa_set syzbot
2023-05-07 11:03 ` syzbot
2024-03-05 10:17 ` Tetsuo Handa
2024-03-05 10:27 ` syzbot
2024-03-05 10:55 ` Tetsuo Handa
2024-03-05 11:04 ` syzbot
2024-04-05 11:42 ` Tetsuo Handa
2024-04-05 11:44 ` [syzbot] [arm] " syzbot
2024-04-05 14:02 ` [syzbot] [hardening?] [mm?] " Tetsuo Handa
2024-04-05 14:25 ` syzbot [this message]
2024-03-05 11:27 ` Tetsuo Handa
2024-04-03 16:12 ` Russell King (Oracle)
2024-04-05 14:28 ` Tetsuo Handa
2024-04-15 9:02 ` Mark Rutland
2024-04-15 9:38 ` Tetsuo Handa
2024-04-15 9:44 ` Russell King (Oracle)
2024-04-15 9:58 ` Tetsuo Handa
2024-04-15 10:27 ` Russell King (Oracle)
2024-04-15 11:43 ` Mark Rutland
2024-04-15 17:02 ` Kees Cook
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=000000000000c5572506155a38b8@google.com \
--to=syzbot+cb76c2983557a07cdb14@syzkaller.appspotmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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