From: David Ahern <dsahern@kernel.org>
To: Tadeusz Struk <tadeusz.struk@linaro.org>,
David Laight <David.Laight@ACULAB.COM>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"syzbot+e223cf47ec8ae183f2a0@syzkaller.appspotmail.com"
<syzbot+e223cf47ec8ae183f2a0@syzkaller.appspotmail.com>
Subject: Re: [PATCH] net: ipv6: fix invalid alloclen in __ip6_append_data
Date: Tue, 8 Mar 2022 22:01:27 -0700 [thread overview]
Message-ID: <ff2e1007-5883-5178-6415-326d6ae69c34@kernel.org> (raw)
In-Reply-To: <45522c89-a3b4-4b98-232b-9c69470124a3@linaro.org>
On 3/8/22 12:46 PM, Tadeusz Struk wrote:
> That fails in the same way:
>
> skbuff: skb_over_panic: text:ffffffff83e7b48b len:65575 put:65575
> head:ffff888101f8a000 data:ffff888101f8a088 tail:0x100af end:0x6c0
> dev:<NULL>
> ------------[ cut here ]------------
> kernel BUG at net/core/skbuff.c:113!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 1852 Comm: repro Not tainted
> 5.17.0-rc7-00020-gea4424be1688-dirty #19
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1.fc35
> RIP: 0010:skb_panic+0x173/0x175
>
> I'm not sure how it supposed to help since it doesn't change the
> alloclen at all.
alloclen is a function of fraglen and fraglen is a function of datalen.
next prev parent reply other threads:[~2022-03-09 5:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 0:01 [PATCH] net: ipv6: fix invalid alloclen in __ip6_append_data Tadeusz Struk
2022-03-08 2:58 ` David Laight
2022-03-08 15:43 ` Tadeusz Struk
2022-03-08 18:18 ` David Ahern
2022-03-08 19:46 ` Tadeusz Struk
2022-03-09 5:01 ` David Ahern [this message]
2022-03-09 21:37 ` Tadeusz Struk
2022-03-10 14:39 ` Willem de Bruijn
2022-03-10 16:06 ` Tadeusz Struk
2022-03-10 17:32 ` Willem de Bruijn
2022-03-10 21:14 ` Tadeusz Struk
2022-03-10 22:13 ` [PATCH v2] net: ipv6: fix skb_over_panic " Tadeusz Struk
2022-03-10 22:18 ` David Laight
2022-03-10 22:30 ` Jakub Kicinski
2022-03-10 22:42 ` Tadeusz Struk
2022-03-10 22:43 ` Willem de Bruijn
2022-03-10 23:04 ` Tadeusz Struk
2022-03-10 23:05 ` David Laight
2022-03-10 23:25 ` [PATCH v3] " Tadeusz Struk
2022-03-11 1:49 ` Willem de Bruijn
2022-03-11 3:43 ` Tadeusz Struk
2022-03-12 1:40 ` patchwork-bot+netdevbpf
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=ff2e1007-5883-5178-6415-326d6ae69c34@kernel.org \
--to=dsahern@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+e223cf47ec8ae183f2a0@syzkaller.appspotmail.com \
--cc=tadeusz.struk@linaro.org \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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.