From: Jens Axboe <axboe@kernel.dk>
To: Eric Sandeen <sandeen@redhat.com>, fio@vger.kernel.org
Subject: Re: [PATCH 3/3] fio: server: Warn when listening on network
Date: Thu, 17 Sep 2026 14:45:35 -0600 [thread overview]
Message-ID: <cc91f33f-5153-466a-80db-b2102cbed1c4@kernel.dk> (raw)
In-Reply-To: <53458ab5-5e82-4af0-93ef-d99002c259c2@redhat.com>
On 9/17/26 2:29 PM, Eric Sandeen wrote:
> On 9/17/26 3:01 PM, Jens Axboe wrote:
>> On 9/17/26 1:41 PM, Eric Sandeen wrote:
>>> Make it crystal clear to users at run time that the client/server
>>> protocol should only be used in trusted environments.
>>>
>>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>>> ---
>>> server.c | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/server.c b/server.c
>>> index 34f3f5c0..887ed7ed 100644
>>> --- a/server.c
>>> +++ b/server.c
>>> @@ -2596,6 +2596,13 @@ static int fio_init_server_connection(void)
>>> } else
>>> snprintf(bind_str, sizeof(bind_str), "%s", bind_sock);
>>>
>>> + if (!bind_sock) {
>>> + log_info("fio: WARNING: The fio network protocol is neither "
>>> + "authenticated nor encrypted.\n");
>>> + log_info("fio: WARNING: Use this mode only in trusted "
>>> + "environments.\n");
>>> + }
>>> +
>>> log_info("fio: server listening on %s\n", bind_str);
>>>
>>> if (listen(sk, 4) < 0) {
>>
>> Let's not pollute the log with that - just document it in the...
>> documentation!
>
> Which is implicitly already there in the man page, so it's probably
> covered. Could make it more explicit I suppose, tho that's still
> assuming users will read it, heh.
The only people that will read this one are the ones that see it
in a log, breaking their scripts, not the intended audience.
If it's already documented in the man page, then just point any
report like that at the man page!
>> Like I said in a private email, anyone that runs a fio backend
>> outside of a trusted local/test environment needs to get their
>> head examined. By definition, since it's generally used to open
>> block devices and read/write to them it's run as root. And since
>> the environment should be trusted, so should the clients. Anyone
>> thinking otherwise needs to get their head examined.
>
> I don't disagree. Just floating the idea of making it crystal clear
> at runtime, and like I said, if you don't like the change, I'm
> happy to drop it.
I will just pick up patch 2/3, I think that one is obviously fine.
--
Jens Axboe
next prev parent reply other threads:[~2026-09-17 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 19:41 [PATCH 0/3] Tidy up some client/server behaviors Eric Sandeen
2026-09-17 19:41 ` [PATCH 1/3] client: sanitize FIO_NET_CMD_SENDFILE requests Eric Sandeen
2026-09-17 20:00 ` Jens Axboe
2026-09-17 20:46 ` Eric Sandeen
2026-09-17 20:47 ` Jens Axboe
2026-09-17 19:41 ` [PATCH 2/3] client: don't send uninitialized data in fio_send_file error replies Eric Sandeen
2026-09-17 19:41 ` [PATCH 3/3] fio: server: Warn when listening on network Eric Sandeen
2026-09-17 20:01 ` Jens Axboe
2026-09-17 20:29 ` Eric Sandeen
2026-09-17 20:45 ` Jens Axboe [this message]
2026-09-17 20:46 ` Jens Axboe
2026-09-17 20:47 ` Eric Sandeen
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=cc91f33f-5153-466a-80db-b2102cbed1c4@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sandeen@redhat.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.