From: Gabriel Krisman Bertazi <krisman@suse.de>
To: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
Cc: Jens Axboe <axboe@kernel.dk>, Breno Leitao <leitao@debian.org>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] io_uring/cmd_net: fix too strict requirement on ioctl
Date: Mon, 16 Feb 2026 09:30:12 -0500 [thread overview]
Message-ID: <87ikbw92x7.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20260216-io-uring-fix@fiberby.net> ("Asbjørn Sloth Tønnesen"'s message of "Mon, 16 Feb 2026 10:27:18 +0000")
Asbjørn Sloth Tønnesen <ast@fiberby.net> writes:
> Attempting SOCKET_URING_OP_SETSOCKOPT on an AF_NETLINK socket resulted
> in an -EOPNOTSUPP, as AF_NETLINK doesn't have an ioctl in its struct
> proto, but only in struct proto_ops.
>
> Prior to the blamed commit, io_uring_cmd_sock() only had two cmd_op
> operations, both requiring ioctl, thus the check was warranted.
>
> Since then, 4 new cmd_op operations have been added, none of which
> depend on ioctl. This patch moves the ioctl check, so it only applies
> to the original operations.
>
> AFAICT, the ioctl requirement was unintentional, and it wasn't
> visible in the blamed patch within 3 lines of context.
>
> Cc: stable@vger.kernel.org
> Fixes: a5d2f99aff6b ("io_uring/cmd: Introduce SOCKET_URING_OP_GETSOCKOPT")
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-02-16 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 10:27 [PATCH] io_uring/cmd_net: fix too strict requirement on ioctl Asbjørn Sloth Tønnesen
2026-02-16 14:30 ` Gabriel Krisman Bertazi [this message]
2026-02-16 15:29 ` Jens Axboe
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=87ikbw92x7.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=ast@fiberby.net \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.