From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Arnd Bergmann <arnd@arndb.de>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Jeff Layton <jlayton@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andreas Gruenbacher <agruenba@redhat.com>,
Andy Adamson <andros@netapp.com>, <linux-nfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfs4: fix missing-braces warning
Date: Wed, 19 Oct 2016 14:51:20 -0400 [thread overview]
Message-ID: <e182f70d-c9ba-8e1d-fb7f-b81b2df98401@Netapp.com> (raw)
In-Reply-To: <20161018152141.2774735-1-arnd@arndb.de>
Hi Arnd (and Geert, if you're out there. I keep getting "relay access denied" when I try to CC you),
Thanks for the patches for this issue! I've applied Arnd's version for 4.9-rc* since I think it looks a little cleaner.
Cheers,
Anna
On 10/18/2016 11:21 AM, Arnd Bergmann wrote:
> A bugfix introduced a harmless warning for update_open_stateid:
>
> fs/nfs/nfs4proc.c:1548:2: error: missing braces around initializer [-Werror=missing-braces]
>
> Removing the zero in the initializer will do the right thing here
> and initialize the entire structure to zero.
>
> Fixes: 1393d9612ba0 ("NFSv4: Fix a race when updating an open_stateid")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> fs/nfs/nfs4proc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index ad917bd72b38..7897826d7c51 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -1545,7 +1545,7 @@ static int update_open_stateid(struct nfs4_state *state,
> struct nfs_client *clp = server->nfs_client;
> struct nfs_inode *nfsi = NFS_I(state->inode);
> struct nfs_delegation *deleg_cur;
> - nfs4_stateid freeme = {0};
> + nfs4_stateid freeme = { };
> int ret = 0;
>
> fmode &= (FMODE_READ|FMODE_WRITE);
>
prev parent reply other threads:[~2016-10-19 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 15:21 [PATCH] nfs4: fix missing-braces warning Arnd Bergmann
2016-10-19 18:51 ` Anna Schumaker [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=e182f70d-c9ba-8e1d-fb7f-b81b2df98401@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=agruenba@redhat.com \
--cc=andros@netapp.com \
--cc=arnd@arndb.de \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).