From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Mark Rutland <mark.rutland@arm.com>,
"Russell King (Oracle)" <linux@armlinux.org.uk>,
Kees Cook <keescook@chromium.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
syzbot <syzbot+cb76c2983557a07cdb14@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hardening?] [mm?] BUG: bad usercopy in fpa_set
Date: Mon, 15 Apr 2024 18:38:33 +0900 [thread overview]
Message-ID: <c5a3598d-16dd-4aeb-904e-2084fafef9fe@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <ZhztQ9CvDm3UPgE9@FVFF77S0Q05N>
On 2024/04/15 18:02, Mark Rutland wrote:
> 08626a6056aad824 ("arm: Implement thread_struct whitelist for hardened usercopy")
>
> That commit says that all accesses are bounce-buffered and bypass the check,
> but AFAICT the fpa_set() code hasn't changed since then, so either that was
> wrong or the user_regset_copyin() code has changed.
Then, can we go with https://lkml.kernel.org/r/0b49d91b-511f-449e-b7c3-93b2ccce6c49@I-love.SAKURA.ne.jp ?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Mark Rutland <mark.rutland@arm.com>,
"Russell King (Oracle)" <linux@armlinux.org.uk>,
Kees Cook <keescook@chromium.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
syzbot <syzbot+cb76c2983557a07cdb14@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hardening?] [mm?] BUG: bad usercopy in fpa_set
Date: Mon, 15 Apr 2024 18:38:33 +0900 [thread overview]
Message-ID: <c5a3598d-16dd-4aeb-904e-2084fafef9fe@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <ZhztQ9CvDm3UPgE9@FVFF77S0Q05N>
On 2024/04/15 18:02, Mark Rutland wrote:
> 08626a6056aad824 ("arm: Implement thread_struct whitelist for hardened usercopy")
>
> That commit says that all accesses are bounce-buffered and bypass the check,
> but AFAICT the fpa_set() code hasn't changed since then, so either that was
> wrong or the user_regset_copyin() code has changed.
Then, can we go with https://lkml.kernel.org/r/0b49d91b-511f-449e-b7c3-93b2ccce6c49@I-love.SAKURA.ne.jp ?
next prev parent reply other threads:[~2024-04-15 9:39 UTC|newest]
Thread overview: 30+ 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] [arm] " syzbot
2024-03-05 11:27 ` [syzbot] [hardening?] [mm?] " Tetsuo Handa
2024-03-05 11:27 ` Tetsuo Handa
2024-04-03 16:12 ` Russell King (Oracle)
2024-04-03 16:12 ` Russell King (Oracle)
2024-04-05 14:28 ` Tetsuo Handa
2024-04-05 14:28 ` Tetsuo Handa
2024-04-15 9:02 ` Mark Rutland
2024-04-15 9:02 ` Mark Rutland
2024-04-15 9:38 ` Tetsuo Handa [this message]
2024-04-15 9:38 ` Tetsuo Handa
2024-04-15 9:44 ` Russell King (Oracle)
2024-04-15 9:44 ` Russell King (Oracle)
2024-04-15 9:58 ` Tetsuo Handa
2024-04-15 9:58 ` Tetsuo Handa
2024-04-15 10:27 ` Russell King (Oracle)
2024-04-15 10:27 ` Russell King (Oracle)
2024-04-15 11:43 ` Mark Rutland
2024-04-15 11:43 ` Mark Rutland
2024-04-15 17:02 ` Kees Cook
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=c5a3598d-16dd-4aeb-904e-2084fafef9fe@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=syzbot+cb76c2983557a07cdb14@syzkaller.appspotmail.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.