From: Jeff Layton <jlayton@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-nfs@vger.kernel.org, Bruce Fields <bfields@fieldses.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [bug report] nfsd: Protect session creation and client confirm using client_lock
Date: Tue, 07 Sep 2021 07:00:07 -0400 [thread overview]
Message-ID: <deba812574c9b898f99fc08f0c3fa23e85fc36ca.camel@kernel.org> (raw)
In-Reply-To: <20210907080732.GA20341@kili>
On Tue, 2021-09-07 at 11:07 +0300, Dan Carpenter wrote:
> Hello Jeff Layton,
>
> The patch d20c11d86d8f: "nfsd: Protect session creation and client
> confirm using client_lock" from Jul 30, 2014, leads to the following
> Smatch static checker warning:
>
> net/sunrpc/addr.c:178 rpc_parse_scope_id()
> warn: sleeping in atomic context
>
> net/sunrpc/addr.c
> 161 static int rpc_parse_scope_id(struct net *net, const char *buf,
> 162 const size_t buflen, const char *delim,
> 163 struct sockaddr_in6 *sin6)
> 164 {
> 165 char *p;
> 166 size_t len;
> 167
> 168 if ((buf + buflen) == delim)
> 169 return 1;
> 170
> 171 if (*delim != IPV6_SCOPE_DELIMITER)
> 172 return 0;
> 173
> 174 if (!(ipv6_addr_type(&sin6->sin6_addr) & IPV6_ADDR_LINKLOCAL))
> 175 return 0;
> 176
> 177 len = (buf + buflen) - delim - 1;
> --> 178 p = kmemdup_nul(delim + 1, len, GFP_KERNEL);
> 179 if (p) {
> 180 u32 scope_id = 0;
> 181 struct net_device *dev;
> 182
> 183 dev = dev_get_by_name(net, p);
> 184 if (dev != NULL) {
> 185 scope_id = dev->ifindex;
> 186 dev_put(dev);
> 187 } else {
> 188 if (kstrtou32(p, 10, &scope_id) != 0) {
> 189 kfree(p);
> 190 return 0;
> 191 }
> 192 }
> 193
> 194 kfree(p);
> 195
> 196 sin6->sin6_scope_id = scope_id;
> 197 return 1;
> 198 }
> 199
> 200 return 0;
> 201 }
>
> The call tree is:
>
> nfsd4_setclientid() <- disables preempt
> -> gen_callback()
> -> rpc_uaddr2sockaddr()
> -> rpc_pton()
> -> rpc_pton6()
> -> rpc_parse_scope_id()
>
> The commit added a spin_lock to nfsd4_setclientid().
>
> fs/nfsd/nfs4state.c
> 4023 trace_nfsd_clid_verf_mismatch(conf, rqstp,
> 4024 &clverifier);
> 4025 } else
> 4026 trace_nfsd_clid_fresh(new);
> 4027 new->cl_minorversion = 0;
> 4028 gen_callback(new, setclid, rqstp);
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 4029 add_to_unconfirmed(new);
> 4030 setclid->se_clientid.cl_boot = new->cl_clientid.cl_boot;
> 4031 setclid->se_clientid.cl_id = new->cl_clientid.cl_id;
> 4032 memcpy(setclid->se_confirm.data, new->cl_confirm.data, sizeof(setclid->se_confirm.data));
> 4033 new = NULL;
> 4034 status = nfs_ok;
> 4035 out:
> 4036 spin_unlock(&nn->client_lock);
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This is the new lock.
>
> 4037 if (new)
> 4038 free_client(new);
> 4039 if (unconf) {
> 4040 trace_nfsd_clid_expire_unconf(&unconf->cl_clientid);
> 4041 expire_client(unconf);
> 4042 }
> 4043 return status;
>
> regards,
> dan carpenter
(cc'ing Bruce and Chuck)
Wow that is an oldie, but it does seem to be a legit bug.
Probably we should just make rpc_parse_scope_id use an on-stack buffer
instead of calling kmemdup_nul there. Thoughts?
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2021-09-07 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 8:07 [bug report] nfsd: Protect session creation and client confirm using client_lock Dan Carpenter
2021-09-07 11:00 ` Jeff Layton [this message]
2021-09-07 15:00 ` Chuck Lever III
2021-09-08 21:26 ` Bruce Fields
2021-09-08 21:32 ` Chuck Lever III
2021-09-09 10:19 ` Jeff Layton
2021-09-09 14:31 ` Chuck Lever III
2021-09-09 14:56 ` Jeff Layton
2021-09-14 16:37 ` Bruce Fields
2021-09-14 16:48 ` Chuck Lever III
2021-09-15 14:03 ` Chuck Lever III
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=deba812574c9b898f99fc08f0c3fa23e85fc36ca.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-nfs@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