linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	Peng Tao <tao.peng@primarydata.com>,
	linux-nfs@vger.kernel.org
Subject: Build errors due to 64 bit xchg/cmpxchg operations in fs/nfs/flexfilelayout
Date: Fri, 26 Jun 2015 21:09:37 -0700	[thread overview]
Message-ID: <558E2201.1040003@roeck-us.net> (raw)

Hi,

commits 'pNFS/flexfiles: add layoutstats tracking' and 'pnfs/flexfiles: report layoutstat
regularly' in -next introduce 64 bit xchg and cmpxchg operations. This causes compile
errors with 32 bit builds on architectures which do not support those operations.

arm:shmobile_defconfig:

fs/built-in.o: In function `nfs4_ff_end_busy_timer':
:(.text+0xa7110): undefined reference to `__bad_xchg'
fs/built-in.o: In function `nfs4_ff_layoutstat_start_io':
:(.text+0xa7304): undefined reference to `__bad_cmpxchg'
:(.text+0xa731c): undefined reference to `__bad_cmpxchg'
:(.text+0xa73d8): undefined reference to `__bad_cmpxchg'

xtensa:allmodconfig:

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!

Guenter

             reply	other threads:[~2015-06-27  4:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  4:09 Guenter Roeck [this message]
     [not found] ` <CAHQdGtRURfhjoY0EMGMWQR=Yw-tiKr3PWWZ1YVCu9+u8ff9xFw@mail.gmail.com>
2015-06-27  5:39   ` Build errors due to 64 bit xchg/cmpxchg operations in fs/nfs/flexfilelayout Guenter Roeck

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=558E2201.1040003@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tao.peng@primarydata.com \
    --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).