public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Sachin S. Prabhu" <sprabhu@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Memory corruption in nfs3_xdr_setaclargs()
Date: Tue, 20 Jan 2009 13:15:01 -0500	[thread overview]
Message-ID: <1232475301.7055.14.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <49760685.4030409@redhat.com>

On Tue, 2009-01-20 at 17:14 +0000, Sachin S. Prabhu wrote:
> A mistake in calculating the space left in the header in nfs3_xdr_setaclargs()
> can cause memory corruption when setting a large number of acls.
> 
> Reproducer:
> 
> On Server:
> 1) Create directory /test and set mode 777.
> mkdir /test; chmod 777 /test
> 2) Add 200 users and set default acl for user on /test
> for i in {1..200}; do echo $i; useradd user$i; setfacl -m d:u:user$i:rwx
> /test;done
> 3) Add export /test  in /etc/exports
> /test *(rw)
> 
> On client
> 1) Mount server:/test
> mount server:/test /mnt
> 2) Create large number of directories on the the share.
> cd/mnt; for i in {1..1000}; do mkdir $i; done
> At this point, the client should crash.
> 
> A change in call_header changes the value req->rq_snd_buf->head[0]->iov_len to
> reflect the exact size of the header.
> [PATCH] RPC: Ensure XDR iovec length is initialized correctly in call_header
> 334ccfd545bba9690515f2c5c167d5adb161989b
> 
> The iov_len is set to the size of the header in  call_header().
> req->rq_slen = xdr_adjust_iovec(&req->rq_svec[0], p);
> 
> nfs3_xdr_setaclargs() depends on the older behavior and uses this value when
> calculating the number of ACLs it can fit into the header.
> 
>         /* put as much of the acls into head as possible. */
>         len_in_head = min_t(unsigned int, buf->head->iov_len - base, len);
>         len -= len_in_head;
>         req->rq_slen = xdr_adjust_iovec(req->rq_svec, p + (len_in_head >> 2));
> 
> Since at this stage, iov_len < base, len_in_head will always be set to len. For
> a large number of ACLs, this will end up over-writing other parts of memory on
> the nfs client.
> 
> The following patch which set len_in_head to 0 was tested with the reproducer
> and was found to fix the problem.
> 

Looks alright. Could you please add a s-o-b line?

Cheers
  Trond

> --- fs/nfs/nfs3xdr.c.orig	2009-01-20 15:18:12.000000000 +0000
> +++ fs/nfs/nfs3xdr.c	2009-01-20 15:33:45.000000000 +0000
> @@ -691,7 +691,10 @@ nfs3_xdr_setaclargs(struct rpc_rqst *req
>  	*p++ = htonl(args->mask);
>  	base = (char *)p - (char *)buf->head->iov_base;
>  	/* put as much of the acls into head as possible. */
> -	len_in_head = min_t(unsigned int, buf->head->iov_len - base, len);
> +	if ( buf->head->iov_len > base )
> +		len_in_head = min_t(unsigned int, buf->head->iov_len - base, len);
> +	else
> +		len_in_head = 0;
>  	len -= len_in_head;
>  	req->rq_slen = xdr_adjust_iovec(req->rq_svec, p + (len_in_head >> 2));
> 
> Thanks to Kevin Rudd who did the major legwork here to figure the problem and
> create the patch.
> 
> Sachin Prabhu
> 


  reply	other threads:[~2009-01-20 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 17:14 Memory corruption in nfs3_xdr_setaclargs() Sachin S. Prabhu
2009-01-20 18:15 ` Trond Myklebust [this message]
     [not found]   ` <1232475301.7055.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-01-21 14:55     ` Sachin S. Prabhu
2009-03-05 16:33     ` Kevin W. Rudd
     [not found]       ` <alpine.LFD.1.10.0903050829420.3949-mupu0Q0mUPfkOmf+N4b0O9FgqiXiwxn+0E9HWUfgJXw@public.gmane.org>
2009-03-05 18:53         ` Trond Myklebust
     [not found]           ` <1236279188.13361.30.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-05 19:49             ` Kevin W. Rudd
     [not found]               ` <alpine.LFD.1.10.0903051135040.3949-mupu0Q0mUPfkOmf+N4b0O9FgqiXiwxn+0E9HWUfgJXw@public.gmane.org>
2009-03-06 20:22                 ` Trond Myklebust
     [not found]                   ` <1236370937.7244.52.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-06 22:51                     ` Kevin W. Rudd

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=1232475301.7055.14.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sprabhu@redhat.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