From: Ian Kent <ikent@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [vfs:work.autofs 6/10] ERROR: "path_is_mountpoint" [fs/autofs4/autofs4.ko] undefined!
Date: Sun, 04 Dec 2016 17:28:08 +0800 [thread overview]
Message-ID: <1480843688.7509.3.camel@redhat.com> (raw)
In-Reply-To: <201612040921.wXtI5ecC%fengguang.wu@intel.com>
On Sun, 2016-12-04 at 09:04 +0800, kbuild test robot wrote:
> tree:A A A https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
> work.autofs
> head:A A A 75aa916747375486b99966e78755a382f432d63c
> commit: fee9da65299be1a18829334b6f74d7dd4d688248 [6/10] autofs: use
> path_is_mountpoint() to fix unreliable d_mountpoint() checks
> config: x86_64-randconfig-i0-201649 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
> A A A A A A A A git checkout fee9da65299be1a18829334b6f74d7dd4d688248
> A A A A A A A A # save the attached .config to linux build tree
> A A A A A A A A make ARCH=x86_64A
>
> All errors (new ones prefixed by >>):
>
> >
> > >
> > > ERROR: "path_is_mountpoint" [fs/autofs4/autofs4.ko] undefined!
Oh wait, I did see this when I looked at vfs.git#work.autofs but was more
concerned with the substance of the changes to pay attention to it.
That would be caused by:
bool path_is_mountpoint(const struct path *path)
{
...
}
EXPORT_SYMBOL(__path_is_mountpoint);
Ian
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-04 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 1:04 [vfs:work.autofs 6/10] ERROR: "path_is_mountpoint" [fs/autofs4/autofs4.ko] undefined! kbuild test robot
2016-12-04 9:28 ` Ian Kent [this message]
2016-12-04 15:23 ` Al Viro
2016-12-04 23:31 ` Ian Kent
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=1480843688.7509.3.camel@redhat.com \
--to=ikent@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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).