From: Yajun Deng <yajun.deng@linux.dev>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Yajun Deng <yajun.deng@linux.dev>, Jiri Pirko <jiri@nvidia.com>
Subject: [PATCH net-next v2] net: core: Remove the dup_errno parameter in dev_prep_valid_name()
Date: Thu, 27 Jun 2024 21:41:31 +0800 [thread overview]
Message-ID: <20240627134131.3018-1-yajun.deng@linux.dev> (raw)
netdev_name_in_use() in dev_prep_valid_name() return -EEXIST makes
more sense if it's not NULL, but dev_alloc_name() should keep the
-ENFILE errno.
There are three callers to dev_prep_valid_name(), the dup_errno
parameter is only for dev_alloc_name, it's not necessary for the other
callers.
Remove the dup_errno parameter in dev_prep_valid_name() and add a
conditional operator to dev_alloc_name(), replace -EEXIST with
-ENFILE.
Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
---
v2: Make the commit more detailed.
v1: https://lore.kernel.org/all/20240618131743.2690-1-yajun.deng@linux.dev/
---
net/core/dev.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
index 0a23d7da7fbc..00e8c785e5ee 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -1153,8 +1153,7 @@ static int __dev_alloc_name(struct net *net, const char *name, char *res)
/* Returns negative errno or allocated unit id (see __dev_alloc_name()) */
static int dev_prep_valid_name(struct net *net, struct net_device *dev,
- const char *want_name, char *out_name,
- int dup_errno)
+ const char *want_name, char *out_name)
{
if (!dev_valid_name(want_name))
return -EINVAL;
@@ -1163,7 +1162,7 @@ static int dev_prep_valid_name(struct net *net, struct net_device *dev,
return __dev_alloc_name(net, want_name, out_name);
if (netdev_name_in_use(net, want_name))
- return -dup_errno;
+ return -EEXIST;
if (out_name != want_name)
strscpy(out_name, want_name, IFNAMSIZ);
return 0;
@@ -1185,7 +1184,10 @@ static int dev_prep_valid_name(struct net *net, struct net_device *dev,
int dev_alloc_name(struct net_device *dev, const char *name)
{
- return dev_prep_valid_name(dev_net(dev), dev, name, dev->name, ENFILE);
+ int ret;
+
+ ret = dev_prep_valid_name(dev_net(dev), dev, name, dev->name);
+ return ret == -EEXIST ? -ENFILE : ret;
}
EXPORT_SYMBOL(dev_alloc_name);
@@ -1194,7 +1196,7 @@ static int dev_get_valid_name(struct net *net, struct net_device *dev,
{
int ret;
- ret = dev_prep_valid_name(net, dev, name, dev->name, EEXIST);
+ ret = dev_prep_valid_name(net, dev, name, dev->name);
return ret < 0 ? ret : 0;
}
@@ -11446,7 +11448,7 @@ int __dev_change_net_namespace(struct net_device *dev, struct net *net,
/* We get here if we can't use the current device name */
if (!pat)
goto out;
- err = dev_prep_valid_name(net, dev, pat, new_name, EEXIST);
+ err = dev_prep_valid_name(net, dev, pat, new_name);
if (err < 0)
goto out;
}
--
2.25.1
next reply other threads:[~2024-06-27 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 13:41 Yajun Deng [this message]
2024-06-27 22:03 ` [PATCH net-next v2] net: core: Remove the dup_errno parameter in dev_prep_valid_name() Jakub Kicinski
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=20240627134131.3018-1-yajun.deng@linux.dev \
--to=yajun.deng@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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.