From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: stable: KASan for ARM
Date: Sun, 7 Mar 2021 16:20:25 +0100 [thread overview]
Message-ID: <YETvOfBpfGrzewmt@kroah.com> (raw)
In-Reply-To: <20210307150040.GB28240@qmqm.qmqm.pl>
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?
thanks,
greg k-h
_______________________________________________
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: stable: KASan for ARM
Date: Sun, 7 Mar 2021 16:20:25 +0100 [thread overview]
Message-ID: <YETvOfBpfGrzewmt@kroah.com> (raw)
In-Reply-To: <20210307150040.GB28240@qmqm.qmqm.pl>
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?
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-07 15:22 UTC|newest]
Thread overview: 18+ 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:00 ` Michał Mirosław
2021-03-07 15:20 ` Greg Kroah-Hartman [this message]
2021-03-07 15:20 ` Greg Kroah-Hartman
2021-03-07 16:10 ` Ard Biesheuvel
2021-03-07 16:10 ` Ard Biesheuvel
2021-03-07 22:48 ` Russell King - ARM Linux admin
2021-03-07 22:48 ` Russell King - ARM Linux admin
2021-03-07 23:34 ` Michał Mirosław
2021-03-07 23:34 ` Michał Mirosław
2021-03-08 0:42 ` Sasha Levin
2021-03-08 0:42 ` Sasha Levin
2021-03-08 6:13 ` Greg Kroah-Hartman
2021-03-08 6:13 ` Greg Kroah-Hartman
2021-03-08 9:44 ` Linus Walleij
2021-03-08 9:44 ` Linus Walleij
2021-03-08 22:51 ` Michał Mirosław
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=YETvOfBpfGrzewmt@kroah.com \
--to=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 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.