Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@primarydata.com>
Cc: linux-nfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH v2 0/4] nfsd: clean up sparse endianness warnings
Date: Wed, 18 Jun 2014 11:39:04 -0400	[thread overview]
Message-ID: <20140618153904.GE17790@fieldses.org> (raw)
In-Reply-To: <1403005454-7319-1-git-send-email-jlayton@primarydata.com>

On Tue, Jun 17, 2014 at 07:44:10AM -0400, Jeff Layton wrote:
> This patchset does a number of cleanups to remove sparse warnings that
> appear when -D__CHECK_ENDIAN__ is specified. Mostly, they just add
> __force in the appropriate places to make it clear that casting directly
> to a different endianness is intentional. I've also added comments to
> clarify why we're doing this in the same places.

Applying, thanks for sorting through the sparse output.  May be a few
days before I get a new branch pushed out.

--b.

> 
> Note that there are still some sparse warnings that are not addressed.
> This one looks like a bug in sparse to me. We're initializing different
> slots in an array:
> 
>     fs/nfsd/nfssvc.c:120:10: warning: Initializer entry defined twice
>     fs/nfsd/nfssvc.c:121:10:   also defined here
> 
> This warning is also not addressed in this set:
> 
>     fs/nfsd/auth.c:31:38: warning: incorrect type in argument 1 (different address spaces)
>     fs/nfsd/auth.c:31:38:    expected struct cred const *cred
>     fs/nfsd/auth.c:31:38:    got struct cred const [noderef] <asn:4>*real_cred
> 
> I think sparse is complaining that we're casting away __rcu when handling
> creds. I'm not quite sure whether that's a real bug or not. I've left it alone
> for now until I (or someone else) has some time to look more closely.
> 
> Jeff Layton (4):
>   nfsd: add __force to opaque verifier field casts
>   nfsd: clean up sparse endianness warnings in nfscache.c
>   nfsd: nfsd_splice_read and nfsd_readv should return __be32
>   nfsd: add appropriate __force directives to filehandle generation code
> 
>  fs/nfsd/nfs4proc.c  |  8 ++++++--
>  fs/nfsd/nfs4state.c |  8 ++++++--
>  fs/nfsd/nfscache.c  | 13 +++++++++++--
>  fs/nfsd/nfsfh.c     |  9 ++++++++-
>  fs/nfsd/nfsfh.h     | 15 +++++++++++----
>  fs/nfsd/vfs.c       |  7 ++++---
>  fs/nfsd/vfs.h       |  4 ++--
>  7 files changed, 48 insertions(+), 16 deletions(-)
> 
> -- 
> 1.9.3
> 

      parent reply	other threads:[~2014-06-18 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 11:44 [PATCH v2 0/4] nfsd: clean up sparse endianness warnings Jeff Layton
2014-06-17 11:44 ` [PATCH v2 1/4] nfsd: add __force to opaque verifier field casts Jeff Layton
2014-06-17 13:52   ` Christoph Hellwig
2014-06-17 11:44 ` [PATCH v2 2/4] nfsd: clean up sparse endianness warnings in nfscache.c Jeff Layton
2014-06-17 13:52   ` Christoph Hellwig
2014-06-17 11:44 ` [PATCH v2 3/4] nfsd: nfsd_splice_read and nfsd_readv should return __be32 Jeff Layton
2014-06-17 13:53   ` Christoph Hellwig
2014-06-17 11:44 ` [PATCH v2 4/4] nfsd: add appropriate __force directives to filehandle generation code Jeff Layton
2014-06-17 13:57   ` Christoph Hellwig
2014-06-18 15:39 ` J. Bruce Fields [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=20140618153904.GE17790@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@infradead.org \
    --cc=jlayton@primarydata.com \
    --cc=linux-nfs@vger.kernel.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