From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
edumazet@google.com, jeffreyji@google.com, brianvv@google.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next] net: disable preemption in dev_core_stats_XXX_inc() helpers
Date: Mon, 14 Mar 2022 20:30:11 +0000 [thread overview]
Message-ID: <164728981111.21494.4878273308182979524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220312214505.3294762-1-eric.dumazet@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 12 Mar 2022 13:45:05 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> syzbot was kind enough to remind us that dev->{tx_dropped|rx_dropped}
> could be increased in process context.
>
> BUG: using smp_processor_id() in preemptible [00000000] code: syz-executor413/3593
> caller is netdev_core_stats_alloc+0x98/0x110 net/core/dev.c:10298
> CPU: 1 PID: 3593 Comm: syz-executor413 Not tainted 5.17.0-rc7-syzkaller-02426-g97aeb877de7f #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Call Trace:
> <TASK>
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
> check_preemption_disabled+0x16b/0x170 lib/smp_processor_id.c:49
> netdev_core_stats_alloc+0x98/0x110 net/core/dev.c:10298
> dev_core_stats include/linux/netdevice.h:3855 [inline]
> dev_core_stats_rx_dropped_inc include/linux/netdevice.h:3866 [inline]
> tun_get_user+0x3455/0x3ab0 drivers/net/tun.c:1800
> tun_chr_write_iter+0xe1/0x200 drivers/net/tun.c:2015
> call_write_iter include/linux/fs.h:2074 [inline]
> new_sync_write+0x431/0x660 fs/read_write.c:503
> vfs_write+0x7cd/0xae0 fs/read_write.c:590
> ksys_write+0x12d/0x250 fs/read_write.c:643
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f2cf4f887e3
> Code: 5d 41 5c 41 5d 41 5e e9 9b fd ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 55 c3 0f 1f 40 00 48 83 ec 28 48 89 54 24 18
> RSP: 002b:00007ffd50dd5fd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
> RAX: ffffffffffffffda RBX: 00007ffd50dd6000 RCX: 00007f2cf4f887e3
> RDX: 000000000000002a RSI: 0000000000000000 RDI: 00000000000000c8
> RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007ffd50dd5ff0 R14: 00007ffd50dd5fe8 R15: 00007ffd50dd5fe4
> </TASK>
>
> [...]
Here is the summary with links:
- [net-next] net: disable preemption in dev_core_stats_XXX_inc() helpers
https://git.kernel.org/netdev/net-next/c/fc93db153b01
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:[~2022-03-14 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 21:45 [PATCH net-next] net: disable preemption in dev_core_stats_XXX_inc() helpers Eric Dumazet
2022-03-14 10:32 ` Paolo Abeni
2022-03-14 20:30 ` 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=164728981111.21494.4878273308182979524.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jeffreyji@google.com \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.