From: Su Hui <suhui@nfschina.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: chuck.lever@oracle.com, jlayton@kernel.org, neilb@suse.de,
kolga@netapp.com, Dai.Ngo@oracle.com, tom@talpey.com,
trond.myklebust@hammerspace.com, anna@kernel.org,
nathan@kernel.org, trix@redhat.com, bfields@fieldses.org,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] fs: lockd: avoid possible wrong NULL parameter
Date: Thu, 3 Aug 2023 12:16:40 +0800 [thread overview]
Message-ID: <18edc2c7-2fb0-493b-9a9f-549acce4e87a@nfschina.com> (raw)
In-Reply-To: <CAKwvOdnRwmxGuEidZ=OWxSX60D6ry0Rb__DjSayga6um35Jsrg@mail.gmail.com>
On 2023/8/3 05:40, Nick Desaulniers wrote:
> On Wed, Aug 2, 2023 at 3:25 AM Dan Carpenter <dan.carpenter@linaro.org> wrote:
> I noticed that the function in question already has a guard:
> 322 if (hostname && memchr(hostname, '/', hostname_len) != NULL) {
>
> Which implies that hostname COULD be NULL.
>
> Should this perhaps simply be rewritten as:
>
> if (!hostname)
> return NULL;
> if (memchr(...) != NULL)
> ...
>
> Rather than bury yet another guard for the same check further down in
> the function? Check once and bail early.
Hi, Nick Desaulnier,
This may disrupt the logic of this function. So maybe the past one is better.
322 if (!hostname)
323 return NULL;
^^^^^^^^^^^^
If we return in this place.
324 if (memchr(hostname, '/', hostname_len) != NULL) {
325 if (printk_ratelimit()) {
326 printk(KERN_WARNING "Invalid hostname \"%.*s\" "
327 "in NFS lock request\n",
328 (int)hostname_len, hostname);
329 }
330 return NULL;
331 }
332
333 retry:
334 spin_lock(&nsm_lock);
335
336 if (nsm_use_hostnames && hostname != NULL)
337 cached = nsm_lookup_hostname(&ln->nsm_handles,
338 hostname, hostname_len);
339 else
340 cached = nsm_lookup_addr(&ln->nsm_handles, sap);
^^^^^^^^^^^^^^^
This case will be broken when hostname is NULL.
341
342 if (cached != NULL) {
343 refcount_inc(&cached->sm_count);
344 spin_unlock(&nsm_lock);
345 kfree(new);
346 dprintk("lockd: found nsm_handle for %s (%s), "
347 "cnt %d\n", cached->sm_name,
348 cached->sm_addrbuf,
349 refcount_read(&cached->sm_count));
350 return cached;
351 }
>> I noticed a related bug which Smatch doesn't find, because of how Smatch
>> handles the dprintk macro.
Hi, Dan,
Great eye!
Should I send a separate patch for this bug and add you as Reported-by ?
>>
>> fs/lockd/host.c
>> truct nlm_host *nlmclnt_lookup_host(const struct sockaddr *sap,
>> 217 const size_t salen,
>> 218 const unsigned short protocol,
>> 219 const u32 version,
>> 220 const char *hostname,
>> 221 int noresvport,
>> 222 struct net *net,
>> 223 const struct cred *cred)
>> 224 {
>> 225 struct nlm_lookup_host_info ni = {
>> 226 .server = 0,
>> 227 .sap = sap,
>> 228 .salen = salen,
>> 229 .protocol = protocol,
>> 230 .version = version,
>> 231 .hostname = hostname,
>> 232 .hostname_len = strlen(hostname),
>> ^^^^^^^^
>> Dereferenced
>>
>> 233 .noresvport = noresvport,
>> 234 .net = net,
>> 235 .cred = cred,
>> 236 };
>> 237 struct hlist_head *chain;
>> 238 struct nlm_host *host;
>> 239 struct nsm_handle *nsm = NULL;
>> 240 struct lockd_net *ln = net_generic(net, lockd_net_id);
>> 241
>> 242 dprintk("lockd: %s(host='%s', vers=%u, proto=%s)\n", __func__,
>> 243 (hostname ? hostname : "<none>"), version,
>> ^^^^^^^^
>> Checked too late.
>>
>> 244 (protocol == IPPROTO_UDP ? "udp" : "tcp"));
>> 245
>>
>> regards,
>> dan carpenter
>
>
next prev parent reply other threads:[~2023-08-03 4:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 8:05 Su Hui
2023-08-02 10:25 ` Dan Carpenter
2023-08-02 10:41 ` Dan Carpenter
2023-08-03 3:08 ` Su Hui
2023-08-02 21:40 ` Nick Desaulniers
2023-08-03 4:16 ` Su Hui [this message]
2023-08-03 9:10 ` Dan Carpenter
2023-08-03 9:08 ` Dan Carpenter
[not found] ` <5066885c-3ac9-adbd-6852-eba89657470c@nfschina.com>
2023-08-03 16:38 ` Nick Desaulniers
2023-08-03 16:56 ` Jeff Layton
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=18edc2c7-2fb0-493b-9a9f-549acce4e87a@nfschina.com \
--to=suhui@nfschina.com \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dan.carpenter@linaro.org \
--cc=jlayton@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=neilb@suse.de \
--cc=tom@talpey.com \
--cc=trix@redhat.com \
--cc=trond.myklebust@hammerspace.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
all inboxes | Powered by JetHome®