From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Linus Walleij" <linus.walleij@linaro.org>,
stable@vger.kernel.org,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: stable: KASan for ARM
Date: Sun, 7 Mar 2021 22:48:54 +0000 [thread overview]
Message-ID: <20210307224854.GF1463@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAMj1kXEDD0To+t40ymFTrWVpBJBdi5PXYfxzE3yi5-VjDPTKoA@mail.gmail.com>
On Sun, Mar 07, 2021 at 05:10:43PM +0100, Ard Biesheuvel wrote:
> (+ Russell)
>
> On Sun, 7 Mar 2021 at 16:21, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Sun, Mar 07, 2021 at 04:00:40PM +0100, Michał Mirosław wrote:
> > > Dear Greg,
> > >
> > > Would you consider KASan for ARM patches for LTS (5.10) kernel? Those
> > > are 7a1be318f579..421015713b30 if I understand correctly. They are
> > > not normal stable material, but I think they will help tremendously in
> > > discovering kernel bugs on 32-bit ARMs.
> >
> > Looks like a new feature to me, right?
> >
> > How many patches, and have you tested them? If so, submit them as a
> > patch series and we can review them, but if this is a new feature, it
> > does not meet the stable kernel rules.
> >
> > And why not just use 5.11 or newer for discovering kernel bugs? Why
> > does 5.10 matter here?
> >
>
> The KASan support was rather tricky to get right, so I don't think
> this is suitable for stable. The range 7a1be318f579..421015713b30 is
> definitely not complete (we'd need at least
> e9a2f8b599d0bc22a1b13e69527246ac39c697b4 and
> 10fce53c0ef8f6e79115c3d9e0d7ea1338c3fa37 as well), and the intrusive
> nature of those changes means they are definitely not appropriate as
> stable backports.
I agree - it took quite a while for KASan to settle down - and our last
issue with KASan causing a panic in the Kprobes codes was in February.
So, I think at the very least, requesting to backport this so soon is
premature. That fix is not included even in what you mention above.
Maybe that fix has already been picked up in stable, I don't know.
So, we know that there's probably more to getting kprobes working on
32-bit ARM than even you've mentioned above.
Is it worth backporting such a major feature to stable kernels? Or
would it be better to backport the fixes found by KASan from later
kernels? My feeling is the latter is the better all round approach.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-07 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 15:00 stable: KASan for ARM Michał Mirosław
2021-03-07 15:20 ` Greg Kroah-Hartman
2021-03-07 16:10 ` Ard Biesheuvel
2021-03-07 22:48 ` Russell King - ARM Linux admin [this message]
2021-03-07 23:34 ` Michał Mirosław
2021-03-08 0:42 ` Sasha Levin
2021-03-08 6:13 ` Greg Kroah-Hartman
2021-03-08 9:44 ` Linus Walleij
2021-03-08 22:51 ` Michał Mirosław
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=20210307224854.GF1463@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).