[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190214164937.GC23000@quack2.suse.cz>
Date: Thu, 14 Feb 2019 17:49:37 +0100
From: Jan Kara <jack@...e.cz>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Jan Kara <jack@...e.cz>, Amir Goldstein <amir73il@...il.com>
Subject: Re: linux-next: Tree for Feb 14 (fanotify)
On Thu 14-02-19 07:58:33, Randy Dunlap wrote:
> On 2/13/19 10:51 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190213:
> >
>
> seen on i386:
>
> when # CONFIG_EXPORTFS_BLOCK_OPS is not set:
>
> ld: fs/notify/fanotify/fanotify.o: in function `fanotify_alloc_event':
> fanotify.c:(.text+0x25a): undefined reference to `exportfs_encode_inode_fh'
> ld: fanotify.c:(.text+0x29e): undefined reference to `exportfs_encode_inode_fh'
Yeah, fanotify needs to select EXPORTFS now. Added patch to my tree. Thanks
for report!
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists