Linux NFS development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Frank Sorenson <sorenson@redhat.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] NFS: change sign of nfs_fh length
Date: Tue, 23 Oct 2018 08:40:31 -0700	[thread overview]
Message-ID: <20181023154031.GF20085@bombadil.infradead.org> (raw)
In-Reply-To: <85517ec3-e3d4-1bf3-8eea-cb274face1a7@redhat.com>

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?

  reply	other threads:[~2018-10-23 15:40 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 [this message]
2018-10-23 16:09   ` Trond Myklebust
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=20181023154031.GF20085@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sorenson@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