From: patchwork-bot+netdevbpf@kernel.org
To: Dong Chenchen <dongchenchen2@huawei.com>
Cc: edumazet@google.com, kuba@kernel.org, davem@davemloft.net,
pabeni@redhat.com, simon.horman@corigine.com, jbenc@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yuehaibing@huawei.com, weiyongjun1@huawei.com,
syzbot+632b5d9964208bfef8c0@syzkaller.appspotmail.com
Subject: Re: [PATCH net, v4] net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment()
Date: Mon, 15 May 2023 07:50:19 +0000 [thread overview]
Message-ID: <168413701982.26935.1923610991191473208.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230511125440.1177848-1-dongchenchen2@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 11 May 2023 20:54:40 +0800 you wrote:
> As the call trace shows, skb_panic was caused by wrong skb->mac_header
> in nsh_gso_segment():
>
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
> CPU: 3 PID: 2737 Comm: syz Not tainted 6.3.0-next-20230505 #1
> RIP: 0010:skb_panic+0xda/0xe0
> call Trace:
> skb_push+0x91/0xa0
> nsh_gso_segment+0x4f3/0x570
> skb_mac_gso_segment+0x19e/0x270
> __skb_gso_segment+0x1e8/0x3c0
> validate_xmit_skb+0x452/0x890
> validate_xmit_skb_list+0x99/0xd0
> sch_direct_xmit+0x294/0x7c0
> __dev_queue_xmit+0x16f0/0x1d70
> packet_xmit+0x185/0x210
> packet_snd+0xc15/0x1170
> packet_sendmsg+0x7b/0xa0
> sock_sendmsg+0x14f/0x160
>
> [...]
Here is the summary with links:
- [net,v4] net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment()
https://git.kernel.org/netdev/net/c/c83b49383b59
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:[~2023-05-15 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 12:54 [PATCH net, v4] net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() Dong Chenchen
2023-05-15 7: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=168413701982.26935.1923610991191473208.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dongchenchen2@huawei.com \
--cc=edumazet@google.com \
--cc=jbenc@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=syzbot+632b5d9964208bfef8c0@syzkaller.appspotmail.com \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@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