From: asmadeus@codewreck.org
To: Joshua Murphy <joshuamurphy@posteo.net>
Cc: ericvh@kernel.org, lucho@ionkov.net, linux_oss@crudebyte.com,
v9fs@lists.linux.dev
Subject: Re: [PATCH v3] net/9p/fd: support ipv6 for trans=tcp
Date: Mon, 20 Jan 2025 17:21:39 +0900 [thread overview]
Message-ID: <Z44Hk0FEm5bTx7SZ@codewreck.org> (raw)
In-Reply-To: <20250118192122.327-2-joshuamurphy@posteo.net>
Joshua Murphy wrote on Sat, Jan 18, 2025 at 07:12:36PM +0000:
> Allows specifying an IPv6 address when mounting a remote 9p file system.
>
> Signed-off-by: Joshua Murphy <joshuamurphy@posteo.net>
Thank you!
I don't have any problem with this, I need to find some time to take the
dust off my 9p tcp server setup to try this out.
Meanwhile I should have tried earlier but checkpatch has a few qualms
about style; if you send a v4 for any other reason please try running it
yourself.
--------
$ git show --format=email | ./scripts/checkpatch.pl -
CHECK: No space is necessary after a cast
#56: FILE: net/9p/trans_fd.c:965:
+ ((struct sockaddr_in *) &stor)->sin_addr.s_addr = htonl(INADDR_ANY);
CHECK: No space is necessary after a cast
#58: FILE: net/9p/trans_fd.c:967:
+ ((struct sockaddr_in6 *) &stor)->sin6_addr = in6addr_any;
CHECK: No space is necessary after a cast
#63: FILE: net/9p/trans_fd.c:970:
+ ((struct sockaddr_in *) &stor)->sin_port = htons((ushort)port);
CHECK: No space is necessary after a cast
#65: FILE: net/9p/trans_fd.c:972:
+ ((struct sockaddr_in6 *) &stor)->sin6_port = htons((ushort)port);
CHECK: No space is necessary after a cast
#66: FILE: net/9p/trans_fd.c:973:
+ err = kernel_bind(sock, (struct sockaddr *) &stor, sizeof(stor));
CHECK: Comparison to NULL could be written "!addr"
#89: FILE: net/9p/trans_fd.c:993:
+ if (addr == NULL)
WARNING: braces {} are not necessary for single statement blocks
#95: FILE: net/9p/trans_fd.c:999:
+ if (err < 0) {
+ return err;
+ }
CHECK: No space is necessary after a cast
#117: FILE: net/9p/trans_fd.c:1026:
+ (struct sockaddr *) &stor,
--------
(Some aren't new and I don't mind too much, but most are on new code)
I can't make any promise about testing but will try to find time around
next weekend, after which the patch will slowly make its way in next
cycle.
--
Dominique
next prev parent reply other threads:[~2025-01-20 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 19:12 [PATCH v3] net/9p/fd: support ipv6 for trans=tcp Joshua Murphy
2025-01-20 8:21 ` asmadeus [this message]
2025-01-20 13:13 ` asmadeus
2025-01-20 20:12 ` Joshua Murphy
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=Z44Hk0FEm5bTx7SZ@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=joshuamurphy@posteo.net \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
/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