From: Jakub Kicinski <kuba@kernel.org>
To: mkubecek@suse.cz, andrew@lunn.ch
Cc: netdev@vger.kernel.org, dcavalca@fb.com, filbranden@fb.com,
michel@fb.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH ethtool 2/3] ethtool: use dummy args[] entry for no-args case
Date: Fri, 13 Aug 2021 10:19:37 -0700 [thread overview]
Message-ID: <20210813171938.1127891-3-kuba@kernel.org> (raw)
In-Reply-To: <20210813171938.1127891-1-kuba@kernel.org>
Simplify the code flow further by adding a struct option
entry for the no-args case (e.g. "ethtool eth0").
This leads to a slight change in the help output, there
will now be an extra space between FLAGS and DEVICE in
that case:
ethtool [ FLAGS ] DEVNAME Display standard information about device
but hopefully that's okay.
Note that this patch adds a false-positive warning with GCC 11:
ethtool.c: In function ‘find_option’:
ethtool.c:6082:29: warning: offset ‘1’ outside bounds of constant string [-Warray-bounds]
6082 | opt += len + 1;
| ~~~~^~~~~~~~~~
we'll never get to that code if the string is empty.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
ethtool.c | 34 ++++++++++++++--------------------
1 file changed, 14 insertions(+), 20 deletions(-)
diff --git a/ethtool.c b/ethtool.c
index 8cf1b13e4176..9e02fe4f09a5 100644
--- a/ethtool.c
+++ b/ethtool.c
@@ -5627,6 +5627,13 @@ struct option {
};
static const struct option args[] = {
+ {
+ /* "default" entry when no switch is used */
+ .opts = "",
+ .func = do_gset,
+ .nlfunc = nl_gset,
+ .help = "Display standard information about device",
+ },
{
.opts = "-s|--change",
.func = do_sset,
@@ -6041,10 +6048,7 @@ static int show_usage(struct cmd_context *ctx __maybe_unused)
/* ethtool -h */
fprintf(stdout, PACKAGE " version " VERSION "\n");
- fprintf(stdout,
- "Usage:\n"
- " ethtool [ FLAGS ] DEVNAME\t"
- "Display standard information about device\n");
+ fprintf(stdout, "Usage:\n");
for (i = 0; args[i].opts; i++) {
fputs(" ethtool [ FLAGS ] ", stdout);
fprintf(stdout, "%s %s\t%s\n",
@@ -6287,11 +6291,7 @@ static int ioctl_init(struct cmd_context *ctx, bool no_dev)
int main(int argc, char **argp)
{
- int (*func)(struct cmd_context *);
struct cmd_context ctx = {};
- nl_func_t nlfunc = NULL;
- nl_chk_t nlchk = NULL;
- bool no_dev;
int ret;
int k;
@@ -6345,22 +6345,16 @@ int main(int argc, char **argp)
exit_bad_args();
k = find_option(*argp);
- if (k >= 0) {
+ if (k > 0) {
argp++;
argc--;
- func = args[k].func;
- nlfunc = args[k].nlfunc;
- nlchk = args[k].nlchk;
- no_dev = args[k].no_dev;
} else {
if ((*argp)[0] == '-')
exit_bad_args();
- nlfunc = nl_gset;
- func = do_gset;
- no_dev = false;
+ k = 0;
}
- if (!no_dev) {
+ if (!args[k].no_dev) {
ctx.devname = *argp++;
argc--;
@@ -6369,11 +6363,11 @@ int main(int argc, char **argp)
}
ctx.argc = argc;
ctx.argp = argp;
- netlink_run_handler(&ctx, nlchk, nlfunc, !func);
+ netlink_run_handler(&ctx, args[k].nlchk, args[k].nlfunc, !args[k].func);
- ret = ioctl_init(&ctx, no_dev);
+ ret = ioctl_init(&ctx, args[k].no_dev);
if (ret)
return ret;
- return func(&ctx);
+ return args[k].func(&ctx);
}
--
2.31.1
next prev parent reply other threads:[~2021-08-13 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 17:19 [PATCH ethtool 0/3] ethool: make --json reliable Jakub Kicinski
2021-08-13 17:19 ` [PATCH ethtool 1/3] ethtool: remove questionable goto Jakub Kicinski
2021-08-13 17:19 ` Jakub Kicinski [this message]
2021-08-24 17:41 ` [PATCH ethtool 2/3] ethtool: use dummy args[] entry for no-args case Michal Kubecek
2021-08-24 17:43 ` Jakub Kicinski
2021-08-24 19:46 ` Michal Kubecek
2021-08-13 17:19 ` [PATCH ethtool 3/3] ethtool: return error if command does not support --json Jakub Kicinski
2021-08-24 14:08 ` [PATCH ethtool 0/3] ethool: make --json reliable Jakub Kicinski
2021-08-24 17:30 ` patchwork-bot+netdevbpf
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=20210813171938.1127891-3-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=dcavalca@fb.com \
--cc=filbranden@fb.com \
--cc=michel@fb.com \
--cc=mkubecek@suse.cz \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).