Netdev List
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "Stefano Garzarella" <sgarzare@redhat.com>,
	"David S . Miller" <davem@davemloft.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	"Arseniy Krasnov" <AVKrasnov@sberdevices.ru>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	kvm@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH net] vsock/virtio: fix potential unbounded skb queue
Date: Wed, 6 May 2026 11:49:18 -0400	[thread overview]
Message-ID: <20260506114213-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CANn89iKWhJp2N-60FC4JpX2Dw0sK8-vk2WrHkDOnkgC_c8nbHA@mail.gmail.com>

On Wed, May 06, 2026 at 08:38:39AM -0700, Eric Dumazet wrote:
> On Wed, May 6, 2026 at 8:15 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Tue, May 05, 2026 at 07:14:36AM -0700, Eric Dumazet wrote:
> > > There is always a discrepancy between skb->len and skb->truesize.
> > > You will not be able to announce a 1MB window, and accept one milliion
> > > skb of 1-byte each.
> >
> > We can if we copy.
> 
> You mean, ignore VIRTIO_VSOCK_SEQ_EOM?

No I mean saving it in a compact form.
If packet boundaries are the only concern, the overhead
needn't exceed 50% even for 1 byte messages. asn.1 ber, for
an over-engineered example?


      reply	other threads:[~2026-05-06 15:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 12:26 [PATCH net] vsock/virtio: fix potential unbounded skb queue Eric Dumazet
2026-05-05  2:20 ` patchwork-bot+netdevbpf
2026-05-05 13:51 ` Stefano Garzarella
2026-05-05 14:14   ` Eric Dumazet
2026-05-05 16:11     ` Stefano Garzarella
2026-05-05 16:37       ` Bobby Eshleman
2026-05-06  9:50         ` Arseniy Krasnov
2026-05-06 14:00           ` Stefano Garzarella
2026-05-06 15:37       ` Michael S. Tsirkin
2026-05-07  9:09         ` Stefano Garzarella
2026-05-07 11:45           ` Michael S. Tsirkin
2026-05-07 12:59             ` Stefano Garzarella
2026-05-07 14:33               ` Jakub Kicinski
2026-05-07 16:05                 ` Stefano Garzarella
2026-05-07 16:32                   ` Eric Dumazet
2026-05-07 17:18                     ` Jakub Kicinski
2026-05-08  9:26                       ` Stefano Garzarella
2026-05-07 14:52               ` Michael S. Tsirkin
2026-05-07 22:48               ` Michael S. Tsirkin
2026-05-08  9:41                 ` Stefano Garzarella
2026-05-08  9:43                   ` Michael S. Tsirkin
2026-05-08  9:58                   ` Michael S. Tsirkin
2026-05-08 10:11                     ` Stefano Garzarella
2026-05-06 15:15     ` Michael S. Tsirkin
2026-05-06 15:38       ` Eric Dumazet
2026-05-06 15:49         ` Michael S. Tsirkin [this message]

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=20260506114213-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=AVKrasnov@sberdevices.ru \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox