From: patchwork-bot+netdevbpf@kernel.org
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: edumazet@google.com, kongweibin2@huawei.com, davem@davemloft.net,
kuba@kernel.org, willemb@google.com, asml.silence@gmail.com,
dsahern@kernel.org, vvs@virtuozzo.com, kafai@fb.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
rose.chen@huawei.com, liaichun@huawei.com,
stable@vger.kernel.org
Subject: Re: [PATCH net] ipv6: fix panic when forwarding a pkt with no in6 dev
Date: Mon, 11 Apr 2022 11:30:11 +0000 [thread overview]
Message-ID: <164967661185.4707.11814594786150441538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220408140342.19311-1-nicolas.dichtel@6wind.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 8 Apr 2022 16:03:42 +0200 you wrote:
> kongweibin reported a kernel panic in ip6_forward() when input interface
> has no in6 dev associated.
>
> The following tc commands were used to reproduce this panic:
> tc qdisc del dev vxlan100 root
> tc qdisc add dev vxlan100 root netem corrupt 5%
>
> [...]
Here is the summary with links:
- [net] ipv6: fix panic when forwarding a pkt with no in6 dev
https://git.kernel.org/netdev/net/c/e3fa461d8b0e
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-04-11 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 11:25 [PATCH] ipv6:fix crash when idev is NULL kongweibin
2022-04-07 14:08 ` Eric Dumazet
2022-04-07 16:10 ` Nicolas Dichtel
2022-04-08 14:03 ` [PATCH net] ipv6: fix panic when forwarding a pkt with no in6 dev Nicolas Dichtel
2022-04-08 22:18 ` Eric Dumazet
2022-04-11 6:44 ` 答复: " kongweibin (A)
2022-04-11 1:11 ` David Ahern
2022-04-11 11: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=164967661185.4707.11814594786150441538.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kafai@fb.com \
--cc=kongweibin2@huawei.com \
--cc=kuba@kernel.org \
--cc=liaichun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=rose.chen@huawei.com \
--cc=stable@vger.kernel.org \
--cc=vvs@virtuozzo.com \
--cc=willemb@google.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