linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Peng Tao <tao.peng@primarydata.com>
Cc: Jeff Layton <jeff.layton@primarydata.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	linux-next@vger.kernel.org
Subject: nfs commit breaks build for nfs4.1=y nfs4.2=n
Date: Thu, 25 Jun 2015 10:55:28 -0400	[thread overview]
Message-ID: <20150625145528.GA3069@windriver.com> (raw)


New breakage seen in linux-next:

fs/nfs/pnfs.c:2293: undefined reference to
`nfs42_proc_layoutstats_generic'

...bisected to:

commit 8733408d6ed713d080c325262d7b51a780136d41
Author: Peng Tao <tao.peng@primarydata.com>
Date:   Tue Jun 23 19:51:57 2015 +0800

    pnfs: add pnfs_report_layoutstat helper function

Probably caused by the unusual defconfig having:


$ grep NFS .config
CONFIG_KERNFS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
CONFIG_NFS_V4_1=y			<------------
# CONFIG_NFS_V4_2 is not set		<------------
CONFIG_PNFS_FILE_LAYOUT=y
CONFIG_PNFS_FLEXFILE_LAYOUT=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFSD is not set
CONFIG_NFS_COMMON=y

http://kisskb.ellerman.id.au/kisskb/buildresult/12449989/
    

             reply	other threads:[~2015-06-25 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 14:55 Paul Gortmaker [this message]
2015-06-25 15:24 ` [next] nfs update breaks build on sparc Paul Gortmaker
2015-06-25 22:40   ` Paul Gortmaker
2015-06-25 23:13   ` Trond Myklebust
2015-06-26  1:13     ` Peng Tao
2015-06-25 15:42 ` nfs commit breaks build for nfs4.1=y nfs4.2=n Peng Tao

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=20150625145528.GA3069@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=jeff.layton@primarydata.com \
    --cc=linux-next@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).