From: syzbot <syzbot+f9f8efb58a4db2ca98d0@syzkaller.appspotmail.com>
To: almasrymina@google.com, davem@davemloft.net, edumazet@google.com,
hawk@kernel.org, ilias.apalodimas@linaro.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] general protection fault in page_pool_unlist
Date: Wed, 29 Nov 2023 03:42:07 -0800 [thread overview]
Message-ID: <000000000000584f41060b490648@google.com> (raw)
In-Reply-To: <CANn89i+6BuZA6AjocG_0zTkD1u=pNgZc_DpZMO=yUN=S1cHS3w@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+f9f8efb58a4db2ca98d0@syzkaller.appspotmail.com
Tested on:
commit: f1be1e04 Merge branch '40GbE' of git://git.kernel.org/..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=1333cb78e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=abf6d5a82dab01fe
dashboard link: https://syzkaller.appspot.com/bug?extid=f9f8efb58a4db2ca98d0
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=174c37a4e80000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-11-29 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 11:06 [syzbot] [net?] general protection fault in page_pool_unlist syzbot
2023-11-29 11:14 ` Eric Dumazet
2023-11-29 11:42 ` syzbot [this message]
2023-11-30 6:25 ` [syzbot] [ntfs3?] WARNING in indx_insert_into_buffer syzbot
2023-11-30 7:37 ` [PATCH net-next] net: page_pool: fix null-ptr-deref in page_pool_unlist Lizhi Xu
2023-11-30 8:29 ` Eric Dumazet
2023-11-30 8:58 ` Lizhi Xu
2023-11-30 9:06 ` Eric Dumazet
[not found] <20231130062513.547394-1-lizhi.xu@windriver.com>
2023-11-30 6:46 ` [syzbot] [net?] general protection fault " syzbot
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=000000000000584f41060b490648@google.com \
--to=syzbot+f9f8efb58a4db2ca98d0@syzkaller.appspotmail.com \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.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.