From: "Michael S. Tsirkin" <mst@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: syzbot <syzbot+b4d960daf7a3c7c2b7b1@syzkaller.appspotmail.com>,
davem@davemloft.net, edumazet@google.com, eperezma@redhat.com,
horms@kernel.org, jasowang@redhat.com, kuba@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, sgarzare@redhat.com,
stefanha@redhat.com, syzkaller-bugs@googlegroups.com,
virtualization@lists.linux.dev, xuanzhuo@linux.alibaba.com
Subject: Re: [syzbot] [kvm?] [net?] [virt?] WARNING in virtio_transport_send_pkt_info
Date: Fri, 15 Aug 2025 06:44:47 -0400 [thread overview]
Message-ID: <20250815063140-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <aJ8HVCbE-fIoS1U4@willie-the-truck>
On Fri, Aug 15, 2025 at 11:09:24AM +0100, Will Deacon wrote:
> On Tue, Aug 12, 2025 at 06:15:46AM -0400, Michael S. Tsirkin wrote:
> > On Tue, Aug 12, 2025 at 03:03:02AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> > > WARNING in virtio_transport_send_pkt_info
> >
> > OK so the issue triggers on
> > commit 6693731487a8145a9b039bc983d77edc47693855
> > Author: Will Deacon <will@kernel.org>
> > Date: Thu Jul 17 10:01:16 2025 +0100
> >
> > vsock/virtio: Allocate nonlinear SKBs for handling large transmit buffers
> >
> >
> > but does not trigger on:
> >
> > commit 8ca76151d2c8219edea82f1925a2a25907ff6a9d
> > Author: Will Deacon <will@kernel.org>
> > Date: Thu Jul 17 10:01:15 2025 +0100
> >
> > vsock/virtio: Rename virtio_vsock_skb_rx_put()
> >
> >
> >
> > Will, I suspect your patch merely uncovers a latent bug
> > in zero copy handling elsewhere.
> > Want to take a look?
>
> Sorry for the delay, I was debugging something else!
>
> I see Hillf already tried some stuff in the other thread, but I can take
> a look as well.
>
> Will
I will be frank I don't understand how that patch makes sense though.
--
MST
next prev parent reply other threads:[~2025-08-15 10:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 18:59 [syzbot] [kvm?] [net?] [virt?] WARNING in virtio_transport_send_pkt_info syzbot
2025-08-12 8:39 ` Forwarded: " syzbot
2025-08-12 9:26 ` Michael S. Tsirkin
2025-08-12 9:48 ` syzbot
2025-08-12 9:27 ` Michael S. Tsirkin
2025-08-12 10:03 ` syzbot
2025-08-12 10:15 ` Michael S. Tsirkin
2025-08-15 10:09 ` Will Deacon
2025-08-15 10:44 ` Michael S. Tsirkin [this message]
2025-08-15 12:00 ` Will Deacon
2025-08-15 15:48 ` Will Deacon
2025-08-16 0:08 ` Hillf Danton
2025-08-16 0:30 ` syzbot
2025-08-16 10:34 ` Michael S. Tsirkin
2025-08-18 14:52 ` Will Deacon
2025-08-13 12:41 ` Hillf Danton
2025-08-13 13:03 ` syzbot
2025-08-13 15:43 ` Forwarded: " syzbot
2025-08-13 16:31 ` syzbot
[not found] <20250812040733-mutt-send-email-mst@kernel.org>
2025-08-12 8:55 ` 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=20250815063140-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=syzbot+b4d960daf7a3c7c2b7b1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=virtualization@lists.linux.dev \
--cc=will@kernel.org \
--cc=xuanzhuo@linux.alibaba.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.