Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, johannes.berg@intel.com, mpe@ellerman.id.au,
	j@w1.fi
Subject: Re: [PATCH net-next 4/6] net: trust the bitmap in __dev_alloc_name()
Date: Fri, 20 Oct 2023 12:38:31 +0200	[thread overview]
Message-ID: <ZTJYpx5dn4UPa2/j@nanopsycho> (raw)
In-Reply-To: <20231020011856.3244410-5-kuba@kernel.org>

Fri, Oct 20, 2023 at 03:18:54AM CEST, kuba@kernel.org wrote:
>Prior to restructuring __dev_alloc_name() handled both printf
>and non-printf names. In a clever attempt at code reuse it
>always prints the name into a buffer and checks if it's
>a duplicate.
>
>Trust the bitmap, and return an error if its full.
>
>Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>---
> net/core/dev.c | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
>diff --git a/net/core/dev.c b/net/core/dev.c
>index bbfb02b4a228..d2698b4bbad4 100644
>--- a/net/core/dev.c
>+++ b/net/core/dev.c
>@@ -1119,18 +1119,11 @@ static int __dev_alloc_name(struct net *net, const char *name, char *res)
> 
> 	i = find_first_zero_bit(inuse, max_netdevices);
> 	bitmap_free(inuse);
>+	if (i == max_netdevices)
>+		return -ENFILE;

Hmm, aren't you changeing functionality here? I mean, prior to this
patch, the i of value "max_netdevices" was happily used, wan't it?
In theory it may break things allowing n-1 netdevices of a name instead
of n.


> 
>-	snprintf(buf, IFNAMSIZ, name, i);
>-	if (!netdev_name_in_use(net, buf)) {
>-		strscpy(res, buf, IFNAMSIZ);
>-		return i;
>-	}
>-
>-	/* It is possible to run out of possible slots
>-	 * when the name is long and there isn't enough space left
>-	 * for the digits, or if all bits are used.
>-	 */
>-	return -ENFILE;
>+	snprintf(res, IFNAMSIZ, name, i);
>+	return i;
> }
> 
> /* Returns negative errno or allocated unit id (see __dev_alloc_name()) */
>-- 
>2.41.0
>

  reply	other threads:[~2023-10-20 10:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  1:18 [PATCH net-next 0/6] net: deduplicate netdev name allocation Jakub Kicinski
2023-10-20  1:18 ` [PATCH net-next 1/6] net: don't use input buffer of __dev_alloc_name() as a scratch space Jakub Kicinski
2023-10-20 10:15   ` Jiri Pirko
2023-10-20  1:18 ` [PATCH net-next 2/6] net: make dev_alloc_name() call dev_prep_valid_name() Jakub Kicinski
2023-10-20 10:24   ` Jiri Pirko
2023-10-20 19:01     ` Jakub Kicinski
2023-10-21  7:01       ` Jiri Pirko
2023-10-20  1:18 ` [PATCH net-next 3/6] net: reduce indentation of __dev_alloc_name() Jakub Kicinski
2023-10-20 10:26   ` Jiri Pirko
2023-10-20  1:18 ` [PATCH net-next 4/6] net: trust the bitmap in __dev_alloc_name() Jakub Kicinski
2023-10-20 10:38   ` Jiri Pirko [this message]
2023-10-20 19:04     ` Jakub Kicinski
2023-10-21  7:00       ` Jiri Pirko
2023-10-20  1:18 ` [PATCH net-next 5/6] net: remove dev_valid_name() check from __dev_alloc_name() Jakub Kicinski
2023-10-20 10:39   ` Jiri Pirko
2023-10-20  1:18 ` [PATCH net-next 6/6] net: remove else after return in dev_prep_valid_name() Jakub Kicinski
2023-10-20 10:45   ` Jiri Pirko

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=ZTJYpx5dn4UPa2/j@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=j@w1.fi \
    --cc=johannes.berg@intel.com \
    --cc=kuba@kernel.org \
    --cc=mpe@ellerman.id.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox