From: patchwork-bot+netdevbpf@kernel.org
To: Chen Zhongjin <chenzhongjin@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, daniel@iogearbox.net,
yangyingliang@huawei.com, stephen@networkplumber.org,
wangyuweihx@gmail.com, alexander.mikhalitsyn@virtuozzo.com,
den@openvz.org, xu.xin16@zte.com.cn
Subject: Re: [PATCH net] net, neigh: Fix null-ptr-deref in neigh_table_clear()
Date: Thu, 03 Nov 2022 03:50:16 +0000 [thread overview]
Message-ID: <166744741655.12191.13515055087737354526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221101121552.21890-1-chenzhongjin@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Nov 2022 20:15:52 +0800 you wrote:
> When IPv6 module gets initialized but hits an error in the middle,
> kenel panic with:
>
> KASAN: null-ptr-deref in range [0x0000000000000598-0x000000000000059f]
> CPU: 1 PID: 361 Comm: insmod
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
> RIP: 0010:__neigh_ifdown.isra.0+0x24b/0x370
> RSP: 0018:ffff888012677908 EFLAGS: 00000202
> ...
> Call Trace:
> <TASK>
> neigh_table_clear+0x94/0x2d0
> ndisc_cleanup+0x27/0x40 [ipv6]
> inet6_init+0x21c/0x2cb [ipv6]
> do_one_initcall+0xd3/0x4d0
> do_init_module+0x1ae/0x670
> ...
> Kernel panic - not syncing: Fatal exception
>
> [...]
Here is the summary with links:
- [net] net, neigh: Fix null-ptr-deref in neigh_table_clear()
https://git.kernel.org/netdev/net/c/f8017317cb0b
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-11-03 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 12:15 Chen Zhongjin
2022-11-01 12:37 ` Eric Dumazet
2022-11-01 12:40 ` Denis V. Lunev
2022-11-03 3:50 ` 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=166744741655.12191.13515055087737354526.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=chenzhongjin@huawei.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--cc=wangyuweihx@gmail.com \
--cc=xu.xin16@zte.com.cn \
--cc=yangyingliang@huawei.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
all inboxes | Powered by JetHome®