From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-next@vger.kernel.org, sparclinux@vger.kernel.org
Subject: [next] nfs update breaks build on sparc
Date: Thu, 25 Jun 2015 11:24:24 -0400 [thread overview]
Message-ID: <20150625152424.GC3069@windriver.com> (raw)
In-Reply-To: <20150625145528.GA3069@windriver.com>
New breakage seen in linux-next today:
ERROR: "__xchg_called_with_bad_pointer" [fs/nfs/flexfilelayout/nfs_layout_flexfiles.ko] undefined!
ERROR: "__cmpxchg_called_with_bad_pointer" [fs/nfs/flexfilelayout/nfs_layout_flexfiles.ko] undefined!
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
I tried to reproduce it locally so I could run a bisect,
but it must be toolchain specific because I don't see it.
Paul.
next prev parent reply other threads:[~2015-06-25 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 14:55 nfs commit breaks build for nfs4.1=y nfs4.2=n Paul Gortmaker
2015-06-25 15:24 ` Paul Gortmaker [this message]
2015-06-25 22:40 ` [next] nfs update breaks build on sparc Paul Gortmaker
2015-06-25 23:13 ` Trond Myklebust
2015-06-26 1:13 ` Peng Tao
2015-06-25 15:42 ` nfs commit breaks build for nfs4.1=y nfs4.2=n Peng Tao
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=20150625152424.GC3069@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-next@vger.kernel.org \
--cc=sparclinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).