From: Clement LE GOFFIC <clement.legoffic@foss.st.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Russell King <linux@armlinux.org.uk>, Kees Cook <kees@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Antonio Borneo <antonio.borneo@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] ARM: ioremap: Sync PGDs for VMALLOC shadow
Date: Tue, 29 Oct 2024 16:00:02 +0100 [thread overview]
Message-ID: <aeef0000-2b08-4fd5-b834-0ead5c122223@foss.st.com> (raw)
In-Reply-To: <CACRpkdYtG3ObRCghte2D0UgeZxkOC6oEUg39uRs+Z0nXiPhUTA@mail.gmail.com>
On 10/25/24 22:57, Linus Walleij wrote:
>> What happens if you just
>>
>> git checkout b6506981f880^
>>
>> And build and boot that? It's just running the commit right before the
>> unwinding patch.
>
> Another thing you can test is to disable vmap:ed stacks and see
> what happens. (General architecture-dependent options uncheck
> "Use a virtually-mapped stack".)
Hi Linus,
I have tested your patches against few kernel versions without
reproducing the issue.
- b6506981f880^
- v6.6.48
- v6.12-rc4
I didn't touch to CONFIG_VMAP_STACK though.
The main difference from my crash report is my test environment which
was a downstream one.
So it seems related to ST downstream kernel version based on a v6.6.48.
Even though the backtrace was talking about unwinding and kasan.
I will continue to investigate on my side in the next weeks but I don't
want to block the patch integration process if I was.
Best regards,
Clément
next prev parent reply other threads:[~2024-10-29 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 12:59 [PATCH v3 0/2] Fix KASAN crash when using KASAN_VMALLOC Linus Walleij
2024-10-17 12:59 ` [PATCH v3 1/2] ARM: ioremap: Sync PGDs for VMALLOC shadow Linus Walleij
2024-10-17 14:19 ` Clement LE GOFFIC
2024-10-17 19:00 ` Linus Walleij
2024-10-21 12:09 ` Clement LE GOFFIC
2024-10-21 12:46 ` Linus Walleij
2024-10-24 21:58 ` Linus Walleij
2024-10-25 9:24 ` Clement LE GOFFIC
2024-10-25 11:04 ` Linus Walleij
2024-10-25 20:57 ` Linus Walleij
2024-10-29 15:00 ` Clement LE GOFFIC [this message]
2024-10-29 21:32 ` Linus Walleij
2024-10-17 12:59 ` [PATCH v3 2/2] ARM: entry: Do a dummy read from VMAP shadow Linus Walleij
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=aeef0000-2b08-4fd5-b834-0ead5c122223@foss.st.com \
--to=clement.legoffic@foss.st.com \
--cc=andreyknvl@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=antonio.borneo@foss.st.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=ryabinin.a.a@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox