[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaTfrAwd8yzZLZHfuu7SB0pUTHZ9kUJq+2c2C8RSqpN9w@mail.gmail.com>
Date: Tue, 15 Oct 2024 23:24:31 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>, Clement LE GOFFIC <clement.legoffic@...s.st.com>,
Russell King <linux@...linux.org.uk>,
"Russell King (Oracle)" <rmk+kernel@...linux.org.uk>, Kees Cook <kees@...nel.org>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, Mark Brown <broonie@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
Antonio Borneo <antonio.borneo@...s.st.com>
Subject: Re: Crash on armv7-a using KASAN
On Tue, Oct 15, 2024 at 10:55 PM Linus Walleij <linus.walleij@...aro.org> wrote:
> On Tue, Oct 15, 2024 at 7:28 PM Ard Biesheuvel <ardb@...nel.org> wrote:
>
> > > From a superficial look, it sounds like it should be possible to extend
> > > that to also handle the KASAN shadow of the vmalloc area (which
> > > __check_vmalloc_seq() currently doesn't copy), but I'm not sure of
> > > exactly when we initialise the shadow for a vmalloc allocation relative
> > > to updating vmalloc_seq.
> >
> > Indeed. It appears both vmalloc_seq() and arch_sync_kernel_mappings()
> > need to take the vmalloc shadow into account specifically.
>
> I'm trying to look into that.
I fixed that too and now the KASAN is stabilized. I'll send out the
patches so we get something to test.
Yours,
Linus Walleij
Powered by blists - more mailing lists