All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d8b58d7b0ad89a678a16@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
	 jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
	 linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com,  syzkaller-bugs@googlegroups.com,
	victor@mojatatu.com,  xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] general protection fault in htb_qlen_notify
Date: Thu, 03 Jul 2025 18:12:05 -0700	[thread overview]
Message-ID: <68672a65.a00a0220.c7b3.000c.GAE@google.com> (raw)
In-Reply-To: <f14f4c0f-dc5d-454e-b5ef-1143b5a8f512@mojatatu.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+d8b58d7b0ad89a678a16@syzkaller.appspotmail.com
Tested-by: syzbot+d8b58d7b0ad89a678a16@syzkaller.appspotmail.com

Tested on:

commit:         223e2288 vsock/vmci: Clear the vmci transport packet p..
git tree:       net
console output: https://syzkaller.appspot.com/x/log.txt?x=16685ebc580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=36b0e72cad5298f8
dashboard link: https://syzkaller.appspot.com/bug?extid=d8b58d7b0ad89a678a16
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch:          https://syzkaller.appspot.com/x/patch.diff?x=141d8c8c580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-07-04  1:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  8:17 [syzbot] [net?] general protection fault in htb_qlen_notify syzbot
2025-07-03 11:32 ` syzbot
2025-07-03 15:05   ` Lion, can you take a look at his? WAS(Re: " Jamal Hadi Salim
2025-07-03 16:39     ` Jamal Hadi Salim
2025-07-03 21:06   ` Victor Nogueira
2025-07-04  1:12     ` syzbot [this message]
2025-07-05  5:43 ` 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=68672a65.a00a0220.c7b3.000c.GAE@google.com \
    --to=syzbot+d8b58d7b0ad89a678a16@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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=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.