From: Paolo Abeni <pabeni@redhat.com>
To: Song Chen <chensong_2000@189.cn>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
kory.maincent@bootlin.com, aleksander.lobakin@intel.com,
willemb@google.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/core/dev_ioctl: avoid invoking modprobe with empty ifr_name
Date: Tue, 19 Nov 2024 12:01:34 +0100 [thread overview]
Message-ID: <de23f3cd-833a-44c0-91bc-5a013458a05f@redhat.com> (raw)
In-Reply-To: <20241117045512.111515-1-chensong_2000@189.cn>
On 11/17/24 05:55, Song Chen wrote:
> dev_ioctl handles requests from user space if a process calls
> ioctl(sockfd, SIOCGIFINDEX, &ifr). However, if this user space
> process doesn't have interface name well specified, dev_ioctl
> doesn't give it an essential check, as a result, dev_load will
> invoke modprobe with a nonsense module name if the user happens
> to be sys admin or root, see following code in dev_load:
>
> no_module = !dev;
> if (no_module && capable(CAP_NET_ADMIN))
> no_module = request_module("netdev-%s", name);
> if (no_module && capable(CAP_SYS_MODULE))
> request_module("%s", name);
>
> This patch checks if ifr_name is empty at the beginning, reduces
> the overhead of calling modprobe.
AFAICS technically this optimize a slow path (bad input from the
user-space) at the expense of the more usual path (additional unneeded
conditional) and still AFAICS, there are no functional issues addressed
here.
Note that even the latter more usual path is not a fast path, still the
optimization is not worthy.
/P
next prev parent reply other threads:[~2024-11-19 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 4:55 [PATCH] net/core/dev_ioctl: avoid invoking modprobe with empty ifr_name Song Chen
2024-11-19 11:01 ` Paolo Abeni [this message]
2024-11-25 13:21 ` kernel test robot
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=de23f3cd-833a-44c0-91bc-5a013458a05f@redhat.com \
--to=pabeni@redhat.com \
--cc=aleksander.lobakin@intel.com \
--cc=chensong_2000@189.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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