Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "willy@infradead.org" <willy@infradead.org>,
	"sorenson@redhat.com" <sorenson@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] NFS: change sign of nfs_fh length
Date: Tue, 23 Oct 2018 16:09:39 +0000	[thread overview]
Message-ID: <c3ecb78f39487792cf01f868f2ee8521237b3a33.camel@hammerspace.com> (raw)
In-Reply-To: <20181023154031.GF20085@bombadil.infradead.org>

On Tue, 2018-10-23 at 08:40 -0700, Matthew Wilcox wrote:
> On Tue, Oct 23, 2018 at 10:34:57AM -0500, Frank Sorenson wrote:
> > 
> > The filehandle has a length which is defined as a 32-bit
> > "unsigned integer".  Change sign of the length appropriately.
> > 
> > Signed-off-by: Frank Sorenson <sorenson@redhat.com>
> 
> Is this a cleanup or does it fix a user-visible bug?

It fixes the following comparison:

                if (len > NFS4_FHSIZE)
                        return -EIO;

but in practice, the next line should always catch the buffer overflow
when len is negative:

                p = xdr_inline_decode(xdr, len);
                if (unlikely(!p))
                        goto out_overflow;

That said, it is nice to be redundant, so I'm happy to take the patch.

Frank, in  the future can you please Cc: the maintainers directly on
your patches? I missed this one completely because my mail filter
directed it to my 'linux-fsdevel' inbox rather than 'linux-nfs'...

Thanks,
  Trond

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2018-10-23 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 15:34 [PATCH] NFS: change sign of nfs_fh length Frank Sorenson
2018-10-23 15:40 ` Matthew Wilcox
2018-10-23 16:09   ` Trond Myklebust [this message]
2018-10-23 17:10     ` Benjamin Coddington

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=c3ecb78f39487792cf01f868f2ee8521237b3a33.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sorenson@redhat.com \
    --cc=willy@infradead.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