linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kinglong Mee <kinglongmee@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
	"Linux NFS mailing list" <linux-nfs@vger.kernel.org>
Subject: Re: fuzz tested user mode linux crashed in NFS code path
Date: Wed, 23 Jul 2014 13:04:35 +0800	[thread overview]
Message-ID: <53CF4263.9070506@gmail.com> (raw)
In-Reply-To: <20140721155543.GD8438@fieldses.org>

On 7/21/2014 23:55, J. Bruce Fields wrote:
> On Sat, Jul 19, 2014 at 11:23:59AM +0800, Kinglong Mee wrote:
>> On Sat, Jul 19, 2014 at 12:50 AM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>>> On 07/18/2014 06:22 PM, Toralf Förster wrote:
>>>> I can now try with kzalloc, but due to the nature of this issue I think, that the absence of this crash - even after 2-3 hours - doesn't mean by 100%, that kzalloc fixed it, or ?
>>>
>>> Well, next crash (with kzalloc patch) happened after 20 minutes ...
>>
>> Maybe I have found the problem.
>> The stateid and denied are defined as an union as,
>> fs/nfsd/xdr4.h
>> 145 struct nfsd4_lock_denied {
>> 146         clientid_t      ld_clientid;
>> 147         struct xdr_netobj       ld_owner;
>> 148         u64             ld_start;
>> 149         u64             ld_length;
>> 150         u32             ld_type;
>> 151 };
>> 152
>> 153 struct nfsd4_lock {
>> ... ...
>> 174         /* response */
>> 175         union {
>> 176                 struct {
>> 177                         stateid_t               stateid;
>> 178                 } ok;
>> 179                 struct nfsd4_lock_denied        denied;
>> 180         } u;
>>
>>  30 struct xdr_netobj {
>>  31         unsigned int            len;
>>  32         u8 *                    data;
>>  33 };
>>
>> sizeof(stateid_t) = 16, sizeof(clientid_t) = 8,
>> sizeof(struct xdr_netobj) = 16, (on x86_x64 platform),
>> sizeof(struct xdr_netobj) = 8,  (on i686 platform)
>>
>> Lock file success, nfsd will copy stateid to the union, but the value
>> also influence denied.
>> If on x86_64 platform, only influence the len in xdr_netobj,
>> but on i686 platform, will influence the len and the data in xdr_netobj.
>> So, the problem only appears on i686 platform.
> 
> Oh, great catch, thanks.  Sounds like that would explain all of Toralf's
> results.
> 
> I'll include this explanation with your original patch and submit it for
> 3.16.

I saw the patch in your git-tree, there is one fault about the comments.

> (Note that lock->lk_denied.ld_owner.data appears it should be zero here,
> until you notice that it's one arm of a union the other arm of which is
> written to in the succesful case by the
> 
> memcpy(&oc->oc_resp_stateid, &stp->st_stid.sc_stateid, sizeof(stateid_t));
> 
> in nfsd4_open_confirm(). 

It's, 
 memcpy(&lock->lk_resp_stateid, &lock_stp->st_stid.sc_stateid,
                                sizeof(stateid_t));
in nfsd4_lock().

> In the 32-bit case this overwrites ld_owner.data.)

thanks,
Kinglong Mee

  reply	other threads:[~2014-07-23  5:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 10:32 fuzz tested user mode linux crashed in NFS code path Toralf Förster
2014-07-12 12:31 ` Kinglong Mee
2014-07-12 17:14   ` Toralf Förster
2014-07-16 18:57   ` J. Bruce Fields
2014-07-17 20:27     ` J. Bruce Fields
2014-07-17 20:33       ` Toralf Förster
2014-07-18 16:22       ` Toralf Förster
2014-07-18 16:50         ` Toralf Förster
2014-07-19  3:23           ` Kinglong Mee
2014-07-19  9:27             ` Toralf Förster
2014-07-21 15:55             ` J. Bruce Fields
2014-07-23  5:04               ` Kinglong Mee [this message]
2014-07-23 14:59                 ` J. Bruce Fields

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=53CF4263.9070506@gmail.com \
    --to=kinglongmee@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    /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).