linux-kernel - linux-next: build failure after merge of the nfs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2016 10:48:45 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: linux-next: build failure after merge of the nfs tree

Hi Trond,

After merging the nfs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

fs/nfs/direct.c: In function 'nfs_direct_write_reschedule':
fs/nfs/direct.c:652:32: error: 'struct pnfs_ds_commit_info' has no member named 'nbuckets'
  for (i = 0; i < dreq->ds_cinfo.nbuckets; i++)
                                ^
fs/nfs/direct.c:653:17: error: 'struct pnfs_ds_commit_info' has no member named 'buckets'
   dreq->ds_cinfo.buckets[i].direct_verf.committed = NFS_INVALID_STABLE_HOW;
                 ^

Caused by commit

  2f9273fd2f09 ("NFS: Ensure we reset the write verifier 'committed' value on resend.")

CONFIG_NFS_V4_1 is not set for this build.

I have used the nfs tree from next-20160609 for today.

-- 
Cheers,
Stephen Rothwell