Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Eric Dumazet" <edumazet@google.com>,
	"Arseniy Krasnov" <avkrasnov@salutedevices.com>,
	"Bobby Eshleman" <bobbyeshleman@meta.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"David S . Miller" <davem@davemloft.net>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	"Arseniy Krasnov" <AVKrasnov@sberdevices.ru>,
	"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: Thu, 7 May 2026 07:33:40 -0700	[thread overview]
Message-ID: <20260507073340.0604667d@kernel.org> (raw)
In-Reply-To: <afyMCyBvZpzWrLtO@sgarzare-redhat>

On Thu, 7 May 2026 14:59:13 +0200 Stefano Garzarella wrote:
> >well if you want to support pathological cases such as 1 byte messages
> >that would mean like 100x reduction no?
> 
> Yep, but since this patch is already merged, IMHO that is better than 
> losing data in those pathological cases.

We can revert if you think that the risk of regression is high..
Please LMK soon, we can do it before patch reaches Linus.

  reply	other threads:[~2026-05-07 14:33 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 [this message]
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

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=20260507073340.0604667d@kernel.org \
    --to=kuba@kernel.org \
    --cc=AVKrasnov@sberdevices.ru \
    --cc=avkrasnov@salutedevices.com \
    --cc=bobbyeshleman@meta.com \
    --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=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --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