From: Peter Zijlstra <peterz@infradead.org>
To: Willy Tarreau <w@1wt.eu>
Cc: "zdi-disclosures@trendmicro.com" <zdi-disclosures@trendmicro.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Eric Dumazet <edumazet@kernel.org>,
"security@kernel.org" <security@kernel.org>,
"maintainer:NETWORKING [GENERAL" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
"open list:NETWORKING [GENERAL" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: ZDI-CAN-33367: New Vulnerability Report
Date: Thu, 22 Oct 2026 23:20:25 +0200 [thread overview]
Message-ID: <20261022212025.GV2823843@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <atplVXLEE_mNqhek@1wt.eu>
On Thu, Oct 22, 2026 at 09:34:45PM +0200, Willy Tarreau wrote:
> > We will have some discussions internally, but in the meantime, we will send the cases to you as we always have.
> > If you don't want to do anything with it, that's fine too. We will release the findings at rejection, or 120 days.
> > Whichever comes first.
>
> The main problem we're having is that it's not possible to have anyone on
> your side nor the reporter test a patch. But I won't rehash this, it's not
> new, but *this* is what makes your reports way more painful to deal with
> than many other ones. You (unvoluntarily it seems) act as an insulation
> layer between reporters and develoeprs and that really doesn't help.
This; Willy is far more eloquent than I am, but the zdi reports have
been very painful. And as said; this has been raised a fair number of
times.
next prev parent reply other threads:[~2026-10-22 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 21:46 ZDI-CAN-33367: New Vulnerability Report zdi-disclosures
2026-10-22 4:28 ` Eric Dumazet
2026-10-22 15:28 ` Willem de Bruijn
2026-10-22 16:00 ` Willy Tarreau
2026-10-22 16:02 ` Peter Zijlstra
2026-10-22 18:51 ` zdi-disclosures
2026-10-22 19:34 ` Willy Tarreau
2026-10-22 21:20 ` Peter Zijlstra [this message]
2026-10-26 16:11 ` Jamal Hadi Salim
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=20261022212025.GV2823843@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@kernel.org \
--cc=w@1wt.eu \
--cc=willemdebruijn.kernel@gmail.com \
--cc=zdi-disclosures@trendmicro.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.