Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot <syzbot@syzkaller.appspotmail.com>
To: syzbot@lists.linux.dev
Cc: syzbot <syzbot+cib904ea9ebb647254@syzkaller.appspotmail.com>,
	nogikh@google.com
Subject: Forwarded: Re: [syzbot ci] Re: veth: add Byte Queue Limits (BQL) support
Date: Tue, 14 Apr 2026 01:17:50 -0700	[thread overview]
Message-ID: <69ddf82e.a00a0220.475f0.0038.GAE@google.com> (raw)
In-Reply-To: <20260414081746.17392-1-nogikh@google.com>

For archival purposes, forwarding an incoming command email to
syzbot@lists.linux.dev.

***

Subject: Re: [syzbot ci] Re: veth: add Byte Queue Limits (BQL) support
Author: nogikh@google.com


Hmm, just fixed a problem that may have affected `syz test` processing,
let's try again:


#syz test

---
  drivers/net/veth.c | 4 +++-
  1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/net/veth.c b/drivers/net/veth.c
index 911e7e36e166..9d7b085c9548 100644
--- a/drivers/net/veth.c
+++ b/drivers/net/veth.c
@@ -1138,7 +1138,9 @@ static void veth_napi_del_range(struct net_device
*dev, int start, int end)
         */
        peer = rtnl_dereference(priv->peer);
        if (peer) {
-               for (i = start; i < end; i++)
+               int peer_end = min(end, (int)peer->real_num_tx_queues);
+
+               for (i = start; i < peer_end; i++)
                        netdev_tx_reset_queue(netdev_get_tx_queue(peer, i));
        }


       reply	other threads:[~2026-04-14  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260414081746.17392-1-nogikh@google.com>
2026-04-14  8:17 ` syzbot [this message]
2026-04-14  8:17 ` Forwarded: Re: [syzbot ci] Re: veth: add Byte Queue Limits (BQL) support syzbot
2026-04-14  8:23 ` syzbot
2026-04-14  8:23 ` 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=69ddf82e.a00a0220.475f0.0038.GAE@google.com \
    --to=syzbot@syzkaller.appspotmail.com \
    --cc=nogikh@google.com \
    --cc=syzbot+cib904ea9ebb647254@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox