From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Kees Cook <kees@kernel.org>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Yanjun Yang <yangyj.ee@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Mark Brown <broonie@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
akpm@linux-foundation.org, ben@decadent.org.uk,
Wang Kefeng <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH] ARM: Remove address checking for MMUless devices
Date: Tue, 2 Jul 2024 00:20:39 +0100 [thread overview]
Message-ID: <ZoM5x8xVVGhlcV29@shell.armlinux.org.uk> (raw)
In-Reply-To: <202407011216.E1DCF4BF@keescook>
On Mon, Jul 01, 2024 at 12:17:10PM -0700, Kees Cook wrote:
> On Mon, Jul 01, 2024 at 01:54:21PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > On 12.06.24 03:25, Yanjun Yang wrote:
> > > Apologies for not CCing the relevant maintainers in my previous email.
> > >
> > > On Tue, Jun 11, 2024 at 6:09 PM Yanjun Yang <yangyj.ee@gmail.com> wrote:
> > >>
> > >> Commit 169f9102f9198b ("ARM: 9350/1: fault:
> > >> Implement copy_from_kernel_nofault_allowed()") added the function to check
> > >> address before use. However, for devices without MMU, addr > TASK_SIZE
> > >> will always fail. This patch move this function after the #ifdef
> > >> CONFIG_MMU statement.
> >
> > What happened to this fix regression for a 6.9 regression? From here it
> > looks like it fell through the cracks, but I might be missing something.
>
> This patch can be sent through rmk's ARM patch tracker, but if it's
> urgent, I could take it via my tree? It has Ard's Ack.
I've been so busy with a high priority work issue that I've not been
aware of this email thread until I saw it tonight (because I haven't
been able to read much email!)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2024-07-01 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 10:09 [PATCH] ARM: Remove address checking for MMUless devices Yanjun Yang
2024-06-12 1:25 ` Yanjun Yang
2024-06-12 6:43 ` Ard Biesheuvel
2024-06-12 7:01 ` Yanjun Yang
2024-06-12 7:03 ` Ard Biesheuvel
2024-07-01 11:54 ` Linux regression tracking (Thorsten Leemhuis)
2024-07-01 19:17 ` Kees Cook
2024-07-01 23:20 ` Russell King (Oracle) [this message]
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=ZoM5x8xVVGhlcV29@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=ben@decadent.org.uk \
--cc=broonie@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=regressions@lists.linux.dev \
--cc=wangkefeng.wang@huawei.com \
--cc=yangyj.ee@gmail.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.