From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: UNGLinuxDriver@microchip.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] lan966x: Fix sleeping in atomic context
Date: Thu, 06 Nov 2025 15:40:21 +0000 [thread overview]
Message-ID: <176244362174.255671.6125982381201101043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105074955.1766792-1-horatiu.vultur@microchip.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 5 Nov 2025 08:49:55 +0100 you wrote:
> The following warning was seen when we try to connect using ssh to the device.
>
> BUG: sleeping function called from invalid context at kernel/locking/mutex.c:575
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 104, name: dropbear
> preempt_count: 1, expected: 0
> INFO: lockdep is turned off.
> CPU: 0 UID: 0 PID: 104 Comm: dropbear Tainted: G W 6.18.0-rc2-00399-g6f1ab1b109b9-dirty #530 NONE
> Tainted: [W]=WARN
> Hardware name: Generic DT based system
> Call trace:
> unwind_backtrace from show_stack+0x10/0x14
> show_stack from dump_stack_lvl+0x7c/0xac
> dump_stack_lvl from __might_resched+0x16c/0x2b0
> __might_resched from __mutex_lock+0x64/0xd34
> __mutex_lock from mutex_lock_nested+0x1c/0x24
> mutex_lock_nested from lan966x_stats_get+0x5c/0x558
> lan966x_stats_get from dev_get_stats+0x40/0x43c
> dev_get_stats from dev_seq_printf_stats+0x3c/0x184
> dev_seq_printf_stats from dev_seq_show+0x10/0x30
> dev_seq_show from seq_read_iter+0x350/0x4ec
> seq_read_iter from seq_read+0xfc/0x194
> seq_read from proc_reg_read+0xac/0x100
> proc_reg_read from vfs_read+0xb0/0x2b0
> vfs_read from ksys_read+0x6c/0xec
> ksys_read from ret_fast_syscall+0x0/0x1c
> Exception stack(0xf0b11fa8 to 0xf0b11ff0)
> 1fa0: 00000001 00001000 00000008 be9048d8 00001000 00000001
> 1fc0: 00000001 00001000 00000008 00000003 be905920 0000001e 00000000 00000001
> 1fe0: 0005404c be9048c0 00018684 b6ec2cd8
>
> [...]
Here is the summary with links:
- [net] lan966x: Fix sleeping in atomic context
https://git.kernel.org/netdev/net/c/0216721ce712
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-06 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 7:49 [PATCH net] lan966x: Fix sleeping in atomic context Horatiu Vultur
2025-11-05 22:38 ` Jacob Keller
2025-11-06 15:40 ` patchwork-bot+netdevbpf [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=176244362174.255671.6125982381201101043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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