On Tue, Aug 14, 2018 at 10:34 PM Nick Desaulniers
<ndesaulniers@xxxxxxxxxx> wrote:
>
> +Arnd
>
> On Tue, Aug 14, 2018 at 5:44 AM Andrey Konovalov <andreyknvl@xxxxxxxxxx> wrote:
> > >> > > On Mon, Aug 06, 2018 at 02:08:32PM -0700, Nick Desaulniers wrote:
> > >> > $ git cherry-pick c5caf21ab0cf8
> > >> > $ git cherry-pick 0e410e158e5b
> >
> > I think the issue here is that e7c52b84fb ("kasan: rework Kconfig
> > settings") should have been backported after c5caf21ab0cf8 ("kasan:
> > turn on -fsanitize-address-use-after-scope"). You'll need to
> > "rebackport" the former one (hide use-after-scope under
> > CONFIG_KASAN_EXTRA and set FRAME_WARN to 3072 with KASAN_EXTRA).
>
> It looks like e7c52b84fb is already in the 4.9 tree as commit
> ef3af3465ab4, partially.
>
> Oh, I see what you mean by "rebackport."
>
> Greg, I'm happy to send the patch set. Do you (or anyone else)
> recommend sending a revert of ef3af3465ab4 + a new patch, or just a
> new patch?
>
> Do you expect anything in the commit message that denotes how whether
> a patch applied cleanly or required manual intervention?
I'm missing the background on what you are trying to do here. Do you actually
want to use the -fsanitize-address-use-after-scope feature that got added
later, or do you just need the -fno-builtin option? In the latter case, I think
the easiest solution would be to do a manual backport of 0e410e158e5b
by itself, adjusting for context, and describing what you have done in the
changelog.
Arnd
