All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 22 (ext4 + dax)
Date: Wed, 23 Nov 2016 04:19:35 +1100	[thread overview]
Message-ID: <20161123041935.6644679f@canb.auug.org.au> (raw)
In-Reply-To: <bdfc4395-0df1-15d2-d084-3b84944dcbe7@infradead.org>

Hi Randy,

On Tue, 22 Nov 2016 08:48:39 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> on i386:
> 
> I don't see why this is happening but I reproduced it multiple times.
> 
> fs/built-in.o: In function `ext4_dax_fault':
> file.c:(.text+0x6278b): undefined reference to `dax_iomap_fault'
> file.c:(.text+0x627dc): undefined reference to `dax_iomap_fault'
> fs/built-in.o: In function `ext4_file_write_iter':
> file.c:(.text+0x62bbc): undefined reference to `dax_iomap_rw'
> file.c:(.text+0x62d75): undefined reference to `dax_iomap_rw'
> fs/built-in.o: In function `ext4_file_read_iter':
> file.c:(.text+0x63756): undefined reference to `dax_iomap_rw'
> fs/built-in.o: In function `ext4_block_zero_page_range':
> inode.c:(.text+0x68c24): undefined reference to `iomap_zero_range'
> 
> Full randconfig file is attached.

CONFIG_FS_IOMAP is not set ...

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2016-11-22 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 10:30 linux-next: Tree for Nov 22 Stephen Rothwell
2016-11-22 16:48 ` linux-next: Tree for Nov 22 (ext4 + dax) Randy Dunlap
2016-11-22 17:19   ` Stephen Rothwell [this message]
2016-11-23  4:28     ` Theodore Ts'o

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=20161123041935.6644679f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tytso@mit.edu \
    /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.