From: Stefano Garzarella <sgarzare@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>, Norbert Szetei <norbert@doyensec.com>
Cc: Norbert Szetei <norbert@doyensec.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
John Villamil <john@doyensec.com>
Subject: Re: [PATCH v2 net] vsock: fix buffer size clamping order
Date: Wed, 8 Apr 2026 10:05:06 +0200 [thread overview]
Message-ID: <adYLmNh0_pT4jd1E@sgarzare-redhat> (raw)
In-Reply-To: <20260406173702.56239557@kernel.org>
On Mon, Apr 06, 2026 at 05:37:02PM -0700, Jakub Kicinski wrote:
>On Mon, 6 Apr 2026 22:04:26 +0200 Norbert Szetei wrote:
>> v2: fix indentation/whitespace issues in the previous patch.
>
>This is not a correct way to submit a patch, but please wait until
>Stefano responds with any further postings.
>
I just replied to one of the patch inlined in a reply to the bug report
suggesting some changes.
Please as Jakub suggested, send a new version with at least the Fixes
tag, but follow the process, see
https://docs.kernel.org/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
Feel free to reach me if you need any clarification.
Thanks,
Stefano
next prev parent reply other threads:[~2026-04-08 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 17:28 [BUG] vsock: refcount_t saturation and OOM via buffer size invariant inversion Norbert Szetei
2026-03-31 12:37 ` Stefano Garzarella
2026-04-06 18:41 ` Norbert Szetei
2026-04-06 20:04 ` [PATCH v2 net] vsock: fix buffer size clamping order Norbert Szetei
2026-04-07 0:37 ` Jakub Kicinski
2026-04-08 8:05 ` Stefano Garzarella [this message]
[not found] ` <C918071D-C036-4FD3-BD64-16C8E143479F@doyensec.com>
2026-04-08 8:01 ` [BUG] vsock: refcount_t saturation and OOM via buffer size invariant inversion Stefano Garzarella
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=adYLmNh0_pT4jd1E@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john@doyensec.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=pabeni@redhat.com \
--cc=virtualization@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