From: syzbot <syzbot+a1c17e56a8a62294c714@syzkaller.appspotmail.com>
To: alexanderduyck@fb.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
edumazet@google.com, hawk@kernel.org, john.fastabend@gmail.com,
kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, pabeni@redhat.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, willemb@google.com, yhs@fb.com
Subject: Re: [syzbot] WARNING in pskb_expand_head
Date: Wed, 25 Jan 2023 07:31:19 -0800 [thread overview]
Message-ID: <000000000000ea5ad205f31852e8@google.com> (raw)
In-Reply-To: <0000000000005d4f3205b9ab95f4@google.com>
syzbot suspects this issue was fixed by commit:
commit dbae2b062824fc2d35ae2d5df2f500626c758e80
Author: Paolo Abeni <pabeni@redhat.com>
Date: Wed Sep 28 08:43:09 2022 +0000
net: skb: introduce and use a single page frag cache
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16a58035480000
start commit: bf682942cd26 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=b68d4454cd7c7d91
dashboard link: https://syzkaller.appspot.com/bug?extid=a1c17e56a8a62294c714
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b18438880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120c9038880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: skb: introduce and use a single page frag cache
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-25 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 20:51 WARNING in pskb_expand_head syzbot
2021-01-25 21:12 ` Jakub Kicinski
2021-01-25 22:01 ` Eric Dumazet
2023-01-25 15:31 ` syzbot [this message]
2023-01-27 7:16 ` [syzbot] " Dmitry Vyukov
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=000000000000ea5ad205f31852e8@google.com \
--to=syzbot+a1c17e56a8a62294c714@syzkaller.appspotmail.com \
--cc=alexanderduyck@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willemb@google.com \
--cc=yhs@fb.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.