From: Bryan Schumaker <bjschuma@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: prevent NULL ptr derefs on fault injection
Date: Tue, 27 Nov 2012 12:06:10 -0500 [thread overview]
Message-ID: <50B4F302.8010304@netapp.com> (raw)
In-Reply-To: <20121127170136.GE27142@fieldses.org>
On 11/27/2012 12:01 PM, J. Bruce Fields wrote:
> On Tue, Nov 27, 2012 at 11:31:11AM -0500, Sasha Levin wrote:
>> A recent patch series has moved hashtable initialization to when the net
>> struct is initialized.
>>
>> When injecting faults, we tried accessing the hashtables even if the struct
>> wasn't really initialized (nfsd wasn't in use) - this caused a NULL ptr
>> deref.
>
> Thanks, adding Bryan to cc.--b.
I was just looking over this :). Unfortunately, this patch changes code that my most recent patch set removes so my patches will need to change again if this goes in first. I'm looking for the best place to put this check to avoid having to change each of the forget_something() functions.
- Bryan
>
>>
>> A simple test would be:
>>
>> echo 1 > /sys/kernel/debug/nfsd/forget_locks
>>
>> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
>> ---
>> fs/nfsd/netns.h | 3 +++
>> fs/nfsd/nfs4state.c | 9 +++++++++
>> 2 files changed, 12 insertions(+)
>>
>> diff --git a/fs/nfsd/netns.h b/fs/nfsd/netns.h
>> index 227b93e..c5806a57 100644
>> --- a/fs/nfsd/netns.h
>> +++ b/fs/nfsd/netns.h
>> @@ -83,5 +83,8 @@ struct nfsd_net {
>> struct delayed_work laundromat_work;
>> };
>>
>> +/* Simple check to find out if a given net was properly initialized */
>> +#define nfsd_netns_ready(nn) ((nn)->sessionid_hashtbl)
>> +
>> extern int nfsd_net_id;
>> #endif /* __NFSD_NETNS_H__ */
>> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
>> index e75872f..0e7428c 100644
>> --- a/fs/nfsd/nfs4state.c
>> +++ b/fs/nfsd/nfs4state.c
>> @@ -4598,6 +4598,9 @@ void nfsd_forget_clients(u64 num)
>> int count = 0;
>> struct nfsd_net *nn = net_generic(current->nsproxy->net_ns, nfsd_net_id);
>>
>> + if (!nfsd_netns_ready(nn))
>> + return;
>> +
>> nfs4_lock_state();
>> list_for_each_entry_safe(clp, next, &nn->client_lru, cl_lru) {
>> expire_client(clp);
>> @@ -4643,6 +4646,9 @@ void nfsd_forget_locks(u64 num)
>> int count;
>> struct nfsd_net *nn = net_generic(&init_net, nfsd_net_id);
>>
>> + if (!nfsd_netns_ready(nn))
>> + return;
>> +
>> nfs4_lock_state();
>> count = nfsd_release_n_owners(num, false, release_lockowner_sop, nn);
>> nfs4_unlock_state();
>> @@ -4655,6 +4661,9 @@ void nfsd_forget_openowners(u64 num)
>> int count;
>> struct nfsd_net *nn = net_generic(&init_net, nfsd_net_id);
>>
>> + if (!nfsd_netns_ready(nn))
>> + return;
>> +
>> nfs4_lock_state();
>> count = nfsd_release_n_owners(num, true, release_openowner_sop, nn);
>> nfs4_unlock_state();
>> --
>> 1.8.0
>>
next prev parent reply other threads:[~2012-11-27 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 16:31 [PATCH] nfsd: prevent NULL ptr derefs on fault injection Sasha Levin
2012-11-27 17:01 ` J. Bruce Fields
2012-11-27 17:06 ` Bryan Schumaker [this message]
2012-11-27 17:37 ` Bryan Schumaker
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=50B4F302.8010304@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).