From: syzbot <syzbot+806b0572c8d06b66b234@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
pctammela@mojatatu.com, syzkaller-bugs@googlegroups.com,
victor@mojatatu.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] general protection fault in htb_tcf_block
Date: Sun, 31 Dec 2023 07:04:06 -0800 [thread overview]
Message-ID: <0000000000009ebae1060dcf93f1@google.com> (raw)
In-Reply-To: <1882b96d-0625-4702-b496-161b387d089f@mojatatu.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+806b0572c8d06b66b234@syzkaller.appspotmail.com
Tested on:
commit: 92de776d Merge tag 'mlx5-updates-2023-12-20' of git://..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=141ab32de80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4e9ca8e3c104d2a
dashboard link: https://syzkaller.appspot.com/bug?extid=806b0572c8d06b66b234
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=14e64091e80000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-12-31 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 11:04 [syzbot] [net?] general protection fault in htb_tcf_block syzbot
2023-12-31 14:38 ` Victor Nogueira
2023-12-31 15:04 ` syzbot [this message]
2024-01-04 11:44 ` [syzbot] " syzbot
[not found] <ZZaaH6ToPq6xsJVC@nanopsycho>
2024-01-04 12:36 ` 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=0000000000009ebae1060dcf93f1@google.com \
--to=syzbot+806b0572c8d06b66b234@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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.