From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>
Subject: Re: [BUILD FAILURE] nfs4state.c fails to compile with gcc 4.5.4
Date: Wed, 29 Nov 2017 23:05:28 -0500 [thread overview]
Message-ID: <20171129230528.6955b58a@vmware.local.home> (raw)
In-Reply-To: <CA+55aFxDuQN4EBxNtv+T3c6o0SDCtqEZavXPbuRzYMANb61Wug@mail.gmail.com>
On Wed, 29 Nov 2017 19:44:33 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
I keep older compilers around to test ftrace before -mfentry was
introduced.
I wonder if I should just add a config to force the use without
-mfentry even if the compiler supports it.
> fs/nfs/nfs4state.c | 3 +--
> include/linux/nfs4.h | 2 +-
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index 54fd56d715a8..9db5d0d57fcb 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -71,8 +71,7 @@ const nfs4_stateid zero_stateid = {
> };
> const nfs4_stateid invalid_stateid = {
> {
> - .seqid = cpu_to_be32(0xffffffffU),
> - .other = { 0 },
> + { .seqid = cpu_to_be32(0xffffffffU), .other = { 0 }, },
I tried this and it failed.
> },
> .type = NFS4_INVALID_STATEID_TYPE,
> };
> diff --git a/include/linux/nfs4.h b/include/linux/nfs4.h
> index 47adac640191..e394ba0cd6c5 100644
> --- a/include/linux/nfs4.h
> +++ b/include/linux/nfs4.h
> @@ -53,11 +53,11 @@ typedef struct { char data[NFS4_VERIFIER_SIZE]; } nfs4_verifier;
>
> struct nfs4_stateid_struct {
> union {
> - char data[NFS4_STATEID_SIZE];
> struct {
> __be32 seqid;
> char other[NFS4_STATEID_OTHER_SIZE];
> } __attribute__ ((packed));
> + char data[NFS4_STATEID_SIZE];
But I didn't try this. This looks to be the key.
This works for me.
Tested-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
> };
>
> enum {
next prev parent reply other threads:[~2017-11-30 4:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 2:58 Steven Rostedt
2017-11-30 3:27 ` Linus Torvalds
2017-11-30 3:39 ` Andrew Morton
2017-11-30 3:44 ` Linus Torvalds
2017-11-30 3:48 ` Andrew Morton
2017-11-30 4:05 ` Steven Rostedt [this message]
2017-11-30 11:46 ` Trond Myklebust
2017-11-30 13:05 ` Anna Schumaker
2017-11-30 12:28 ` Arnd Bergmann
2017-11-30 15:55 ` Marc Zyngier
2017-11-30 10:33 ` David Laight
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=20171129230528.6955b58a@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=Anna.Schumaker@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.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
all inboxes | Powered by JetHome®