From: David Gow <davidgow@google.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Brendan Higgins <brendan.higgins@linux.dev>,
Rae Moar <rmoar@google.com>, Huacai Chen <chenhuacai@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: [PATCH v3 1/2] MIPS: Don't crash in stack_top() for tasks without ABI or vDSO
Date: Tue, 15 Apr 2025 16:26:30 +0800 [thread overview]
Message-ID: <CABVgOSkd4v7EE2YSVVb9pezYdhZvY+6=8mbHex+CtFCp8FjGDw@mail.gmail.com> (raw)
In-Reply-To: <20250415-kunit-mips-v3-1-4ec2461b5a7e@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]
On Tue, 15 Apr 2025 at 15:10, Thomas Weißschuh
<thomas.weissschuh@linutronix.de> wrote:
>
> Not all tasks have an ABI associated or vDSO mapped,
> for example kthreads never do.
> If such a task ever ends up calling stack_top(), it will derefence the
> NULL ABI pointer and crash.
>
> This can for example happen when using kunit:
>
> mips_stack_top+0x28/0xc0
> arch_pick_mmap_layout+0x190/0x220
> kunit_vm_mmap_init+0xf8/0x138
> __kunit_add_resource+0x40/0xa8
> kunit_vm_mmap+0x88/0xd8
> usercopy_test_init+0xb8/0x240
> kunit_try_run_case+0x5c/0x1a8
> kunit_generic_run_threadfn_adapter+0x28/0x50
> kthread+0x118/0x240
> ret_from_kernel_thread+0x14/0x1c
>
> Only dereference the ABI point if it is set.
>
> Also move the randomization adjustment into the same conditional.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
This looks good to me -- we've hit what's effectively the same issue
on other architectures with this test, with similar resolutions.
Reviewed-by: David Gow <davidgow@google.com>
I'm happy to have this (and the following path) go in via the KUnit
tree, but if you'd rather have it go via MIPS, that's fine, too. (The
qemu_configs won't generate any merge conflicts.)
-- David
> arch/mips/kernel/process.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c
> index b630604c577f9ff3f2493b0f254363e499c8318c..02aa6a04a21da437909eeac4f149155cc298f5b5 100644
> --- a/arch/mips/kernel/process.c
> +++ b/arch/mips/kernel/process.c
> @@ -690,18 +690,20 @@ unsigned long mips_stack_top(void)
> }
>
> /* Space for the VDSO, data page & GIC user page */
> - top -= PAGE_ALIGN(current->thread.abi->vdso->size);
> - top -= PAGE_SIZE;
> - top -= mips_gic_present() ? PAGE_SIZE : 0;
> + if (current->thread.abi) {
> + top -= PAGE_ALIGN(current->thread.abi->vdso->size);
> + top -= PAGE_SIZE;
> + top -= mips_gic_present() ? PAGE_SIZE : 0;
> +
> + /* Space to randomize the VDSO base */
> + if (current->flags & PF_RANDOMIZE)
> + top -= VDSO_RANDOMIZE_SIZE;
> + }
>
> /* Space for cache colour alignment */
> if (cpu_has_dc_aliases)
> top -= shm_align_mask + 1;
>
> - /* Space to randomize the VDSO base */
> - if (current->flags & PF_RANDOMIZE)
> - top -= VDSO_RANDOMIZE_SIZE;
> -
> return top;
> }
>
>
> --
> 2.49.0
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5281 bytes --]
next prev parent reply other threads:[~2025-04-15 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:10 [PATCH v3 0/2] kunit: qemu_configs: Add MIPS configurations Thomas Weißschuh
2025-04-15 7:10 ` [PATCH v3 1/2] MIPS: Don't crash in stack_top() for tasks without ABI or vDSO Thomas Weißschuh
2025-04-15 8:26 ` David Gow [this message]
2025-04-15 8:47 ` Huacai Chen
2025-04-15 8:57 ` Thomas Weißschuh
2025-04-15 7:10 ` [PATCH v3 2/2] kunit: qemu_configs: Add MIPS configurations Thomas Weißschuh
2025-04-15 8:26 ` David Gow
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='CABVgOSkd4v7EE2YSVVb9pezYdhZvY+6=8mbHex+CtFCp8FjGDw@mail.gmail.com' \
--to=davidgow@google.com \
--cc=brendan.higgins@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rmoar@google.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=tsbogend@alpha.franken.de \
/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).