public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Stefan Wiehler <stefan.wiehler@nokia.com>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] mips: mm: Allocate tlb_vpn array atomically
Date: Wed, 1 Apr 2026 22:27:43 +0200	[thread overview]
Message-ID: <ac1_v3KMngpw-FDB@alpha.franken.de> (raw)
In-Reply-To: <20260310104024.3554197-1-stefan.wiehler@nokia.com>

On Tue, Mar 10, 2026 at 11:40:24AM +0100, Stefan Wiehler wrote:
> Found by DEBUG_ATOMIC_SLEEP:
> 
>   BUG: sleeping function called from invalid context at /include/linux/sched/mm.h:306
>   in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
>   preempt_count: 1, expected: 0
>   RCU nest depth: 0, expected: 0
>   no locks held by swapper/1/0.
>   irq event stamp: 0
>   hardirqs last  enabled at (0): [<0000000000000000>] 0x0
>   hardirqs last disabled at (0): [<ffffffff801477fc>] copy_process+0x75c/0x1b68
>   softirqs last  enabled at (0): [<ffffffff801477fc>] copy_process+0x75c/0x1b68
>   softirqs last disabled at (0): [<0000000000000000>] 0x0
>   CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.6.119-d79e757675ec-fct #1
>   Stack : 800000000290bad8 0000000000000000 0000000000000008 800000000290bae8
>           800000000290bae8 800000000290bc78 0000000000000000 0000000000000000
>           ffffffff80c80000 0000000000000001 ffffffff80d8dee8 ffffffff810d09c0
>           784bb2a7ec10647d 0000000000000010 ffffffff80a6fd60 8000000001d8a9c0
>           0000000000000000 0000000000000000 ffffffff80d90000 0000000000000000
>           ffffffff80c9e0e8 0000000007ffffff 0000000000000cc0 0000000000000400
>           ffffffffffffffff 0000000000000001 0000000000000002 ffffffffc0149ed8
>           fffffffffffffffe 8000000002908000 800000000290bae0 ffffffff80a81b74
>           ffffffff80129fb0 0000000000000000 0000000000000000 0000000000000000
>           0000000000000000 0000000000000000 ffffffff80129fd0 0000000000000000
>           ...
>   Call Trace:
>   [<ffffffff80129fd0>] show_stack+0x60/0x158
>   [<ffffffff80a7f894>] dump_stack_lvl+0x88/0xbc
>   [<ffffffff8018d3c8>] __might_resched+0x268/0x288
>   [<ffffffff803648b0>] __kmem_cache_alloc_node+0x2e0/0x330
>   [<ffffffff80302788>] __kmalloc+0x58/0xd0
>   [<ffffffff80a81b74>] r4k_tlb_uniquify+0x7c/0x428
>   [<ffffffff80143e8c>] tlb_init+0x7c/0x110
>   [<ffffffff8012bdb4>] per_cpu_trap_init+0x16c/0x1d0
>   [<ffffffff80133258>] start_secondary+0x28/0x128
> 
> Fixes: 231ac951faba ("MIPS: mm: kmalloc tlb_vpn array to avoid stack overflow")
> Signed-off-by: Stefan Wiehler <stefan.wiehler@nokia.com>
> Cc: stable@vger.kernel.org
> ---
>  arch/mips/mm/tlb-r4k.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

applied to mips-fixes

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2026-04-01 20:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 10:40 [PATCH] mips: mm: Allocate tlb_vpn array atomically Stefan Wiehler
2026-04-01 20:27 ` Thomas Bogendoerfer [this message]

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=ac1_v3KMngpw-FDB@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=stable@vger.kernel.org \
    --cc=stefan.wiehler@nokia.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