All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Olaf Kirch <okir@suse.de>
Cc: NeilBrown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: [PATCH kNFSd 1 of 4] Fixed possibly xdr parsing error if write size exceed 2^31
Date: Tue, 12 Jul 2005 03:42:43 -0300	[thread overview]
Message-ID: <20050712064243.GA15802@dmt.cnet> (raw)
In-Reply-To: <20050711095015.GA9650@suse.de>

Hi Olaf,

On Mon, Jul 11, 2005 at 11:50:16AM +0200, Olaf Kirch wrote:
> Hi all,
> 
> what happened to this patch? It never seems to have made it
> upstream.

I think it did, long ago:

nfs3xdr.c  	1.10  	CSets  	11 months 	neilb 	Fixed possibly xdr parsing error if write size exceed 2^31

> 
> Olaf
> 
> On Mon, Aug 16, 2004 at 01:58:43PM +1000, NeilBrown wrote:
> > 
> > xdr_argsize_check needs to cope with the possibility that the
> > pointer has wrapped and could be below buf->base.
> > 
> > Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
> > 
> > ### Diffstat output
> >  ./fs/nfsd/nfs3xdr.c         |    2 +-
> >  ./include/linux/nfsd/xdr3.h |    2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff ./fs/nfsd/nfs3xdr.c~current~ ./fs/nfsd/nfs3xdr.c
> > --- ./fs/nfsd/nfs3xdr.c~current~	2004-08-14 13:21:52.000000000 +1000
> > +++ ./fs/nfsd/nfs3xdr.c	2004-08-14 13:23:06.000000000 +1000
> > @@ -273,7 +273,7 @@ xdr_argsize_check(struct svc_rqst *rqstp
> >  {
> >  	struct svc_buf	*buf = &rqstp->rq_argbuf;
> >  
> > -	return p - buf->base <= buf->buflen;
> > +	return p >= buf->base && p <= buf->base + buf->buflen ;
> >  }
> >  
> >  static inline int
> > 
> > diff ./include/linux/nfsd/xdr3.h~current~ ./include/linux/nfsd/xdr3.h
> > --- ./include/linux/nfsd/xdr3.h~current~	2004-08-14 13:17:07.000000000 +1000
> > +++ ./include/linux/nfsd/xdr3.h	2004-08-16 09:48:43.000000000 +1000
> > @@ -41,7 +41,7 @@ struct nfsd3_writeargs {
> >  	__u32			count;
> >  	int			stable;
> >  	__u8 *			data;
> > -	int			len;
> > +	__u32			len;
> >  };
> >  
> >  struct nfsd3_createargs {


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2005-07-12 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  3:58 [PATCH kNFSd 0 of 4] Introduction NeilBrown
2004-08-16  3:58 ` [PATCH kNFSd 3 of 4] Allow larger NFSd MAXBLKSIZE on architectures with larger PAGE_SIZE NeilBrown
2004-08-16  3:58 ` [PATCH kNFSd 2 of 4] mark NFS/TCP not EXPERIMENTAL NeilBrown
2004-08-16  3:58 ` [PATCH kNFSd 4 of 4] Use llseek instead of f_pos= for directory seeking NeilBrown
2004-08-16  9:21   ` Christoph Hellwig
2004-08-16  9:23     ` Christoph Hellwig
2004-08-16  3:58 ` [PATCH kNFSd 1 of 4] Fixed possibly xdr parsing error if write size exceed 2^31 NeilBrown
2005-07-11  9:50   ` Olaf Kirch
2005-07-12  6:42     ` Marcelo Tosatti [this message]

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=20050712064243.GA15802@dmt.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.