From: Trond Myklebust <trondmy@kernel.org>
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: Anna Schumaker <anna@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] pnfs/blocklayout: reject zero chunk_size and volumes_count in GETDEVICEINFO
Date: Tue, 14 Jul 2026 11:38:59 -0400 [thread overview]
Message-ID: <15b4d5a56e560d8b209f5ba7baa85473081e0743.camel@kernel.org> (raw)
In-Reply-To: <CAJJ9bXx0HXLRZoDRBhMytZmifwG+V9fi3LL9Sj49DYoeh7-Ajw@mail.gmail.com>
On Tue, 2026-07-14 at 10:41 -0400, Michael Bommarito wrote:
> On Tue, Jul 14, 2026 at 10:37 AM Trond Myklebust <trondmy@kernel.org>
> wrote:
> > NACK to this, and all further patches with the words "malicious
> > server"
> > as their justification. It's time to stop this incessant flood of
> > worthless AI slop...
>
> Sure, I hear you. I'll make a note to skip your subsystem going
> forward.
>
> FWIW though, these are often exacty the networks where ARP spoofing
> still works and malicious server can be read to mean "anyone who can
> pretend to be a server/peer" for the relevant packet/session.
>
> Thanks,
> Mike
Then seeing this is a great opportunity to discover that you have an
insecure network, and that you should have been using either krb5i,
krb5p, TLS or secure VLAN technology to protect your on-the-wire
message protocols against precisely this kind of man-in-the-middle
attack.
Again, though, a savvy man-in-the-middle won't be trying to cause
clients to crash when they have a golden opportunity to manipulate the
stored data instead.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
prev parent reply other threads:[~2026-07-14 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 15:05 Michael Bommarito
2026-07-14 14:37 ` Trond Myklebust
2026-07-14 14:41 ` Michael Bommarito
2026-07-14 15:38 ` Trond Myklebust [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=15b4d5a56e560d8b209f5ba7baa85473081e0743.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®