9p: fix privport option setting wrong RDMA field

While reviewing a patch adding vsock transport to 9p, I noticed that
since commit 1f3e4142c0 ("9p: convert to the new mount API"), the
Opt_privport case incorrectly sets rdma_opts->port instead of
rdma_opts->privport, so mounting with the privport option overwrites
the RDMA port number instead of enabling privileged port usage.

Fixes: 1f3e4142c0 ("9p: convert to the new mount API")
Cc: stable@vger.kernel.org
Cc: sandeen@redhat.com
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Acked-by: Eric Sandeen <sandeen@redhat.com>
Message-ID: <20260703102254.114446-1-sgarzare@redhat.com>
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
This commit is contained in:
Stefano Garzarella 2026-07-03 12:22:54 +02:00 committed by Dominique Martinet
parent 37dce65a0b
commit 7fb9bd3659

View File

@ -406,7 +406,7 @@ int v9fs_parse_param(struct fs_context *fc, struct fs_parameter *param)
break;
case Opt_privport:
fd_opts->privport = true;
rdma_opts->port = true;
rdma_opts->privport = true;
break;
}