linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the fscache tree
@ 2014-02-06  1:08 Stephen Rothwell
  2014-02-06 17:17 ` David Howells
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2014-02-06  1:08 UTC (permalink / raw)
  To: David Howells; +Cc: linux-next, linux-kernel, John Huston

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Hi David,

After merging the fscache tree, today's linux-next build (x86_64
allmodconfig) failed like this:

fs/cachefiles/bind.c: In function 'cachefiles_daemon_unbind':
fs/cachefiles/bind.c:361:4: error: too few arguments to function 'vfs_unlink'
    ret = vfs_unlink(cache->root->d_inode, dentry);
    ^
In file included from fs/cachefiles/bind.c:18:0:
include/linux/fs.h:1458:12: note: declared here
 extern int vfs_unlink(struct inode *, struct dentry *, struct inode **);
            ^

Caused by commit ab3d73f3ce3d ("Cachefiles: Add features that make sanity
checking easier") from the fscache tree interacting with commit
b21996e36c8e ("locks: break delegations on unlink") from Linus' tree
(which entered Linus' tree before v3.13-rc1).  Does this build for you?

I have used the fscache tree from next-20140205 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: build failure after merge of the fscache tree
  2014-02-06  1:08 linux-next: build failure after merge of the fscache tree Stephen Rothwell
@ 2014-02-06 17:17 ` David Howells
  0 siblings, 0 replies; 3+ messages in thread
From: David Howells @ 2014-02-06 17:17 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: dhowells, linux-next, linux-kernel, John Huston

Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the fscache tree, today's linux-next build (x86_64
> allmodconfig) failed like this:

Yep.  I'd forgotten that branch was in linux-next.  I've moved the patches to
fscache-experimental so that they don't pester Fengguang either.

David

^ permalink raw reply	[flat|nested] 3+ messages in thread

* linux-next: build failure after merge of the fscache tree
@ 2022-05-20  1:14 Stephen Rothwell
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2022-05-20  1:14 UTC (permalink / raw)
  To: David Howells; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

Hi all,

After merging the fscache tree, today's linux-next build (x86_64
allmodconfig) failed like this:

fs/cifs/fscache.c: In function 'cifs_fscache_get_inode_cookie':
fs/cifs/fscache.c:106:14: error: 'struct cifsInodeInfo' has no member named 'netfs_ctx'
  106 |         cifsi->netfs_ctx.cache =
      |              ^~
fs/cifs/fscache.c: In function 'cifs_fscache_release_inode_cookie':
fs/cifs/fscache.c:134:22: error: 'struct cifsInodeInfo' has no member named 'netfs_ctx'
  134 |                 cifsi->netfs_ctx.cache = NULL;
      |                      ^~

Caused by commit

  a3457aa9c40f ("netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context")

I have used the fscache tree from next-20220519 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-05-20  1:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-06  1:08 linux-next: build failure after merge of the fscache tree Stephen Rothwell
2014-02-06 17:17 ` David Howells
2022-05-20  1:14 Stephen Rothwell

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).