All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Tao Peng <tao.peng@primarydata.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: Build errors due to 64 bit xchg/cmpxchg operations in fs/nfs/flexfilelayout
Date: Fri, 26 Jun 2015 22:39:06 -0700	[thread overview]
Message-ID: <558E36FA.7050803@roeck-us.net> (raw)
In-Reply-To: <CAHQdGtRURfhjoY0EMGMWQR=Yw-tiKr3PWWZ1YVCu9+u8ff9xFw@mail.gmail.com>

On 06/26/2015 09:15 PM, Trond Myklebust wrote:
>
> On Jun 27, 2015 12:09 AM, "Guenter Roeck" <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>  >
>  > 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
>
> Hi Guenter
>
> Is this still the case with today's update? The latest patch from Tao was intended to remove those calls.
>

Hi Trond,

This is with next-20150626. I'll let you know if it still happens with the next build.

Guenter

      parent reply	other threads:[~2015-06-27  5:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  4:09 Build errors due to 64 bit xchg/cmpxchg operations in fs/nfs/flexfilelayout Guenter Roeck
     [not found] ` <CAHQdGtRURfhjoY0EMGMWQR=Yw-tiKr3PWWZ1YVCu9+u8ff9xFw@mail.gmail.com>
2015-06-27  5:39   ` Guenter Roeck [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=558E36FA.7050803@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.