From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Brauner <brauner@kernel•org>
Cc: David Howells <dhowells@redhat•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the vfs-brauner-fixes tree
Date: Thu, 17 Oct 2024 12:46:35 +1100 [thread overview]
Message-ID: <20241017124635.3298b1c4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
Hi all,
After merging the vfs-brauner-fixes tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
In file included from include/linux/srcu.h:21,
from include/linux/notifier.h:16,
from arch/x86/include/asm/uprobes.h:13,
from include/linux/uprobes.h:50,
from include/linux/mm_types.h:16,
from include/linux/mmzone.h:22,
from include/linux/gfp.h:7,
from include/linux/slab.h:16,
from fs/afs/rxrpc.c:8:
fs/afs/rxrpc.c: In function 'afs_alloc_call':
fs/afs/rxrpc.c:152:42: error: 'const struct afs_call_type' has no member named 'async_rx'
152 | INIT_WORK(&call->async_work, type->async_rx ?: afs_process_async_call);
| ^~
include/linux/workqueue.h:288:34: note: in definition of macro '__INIT_WORK_KEY'
288 | (_work)->func = (_func); \
| ^~~~~
include/linux/workqueue.h:308:9: note: in expansion of macro '__INIT_WORK'
308 | __INIT_WORK((_work), (_func), 0)
| ^~~~~~~~~~~
fs/afs/rxrpc.c:152:9: note: in expansion of macro 'INIT_WORK'
152 | INIT_WORK(&call->async_work, type->async_rx ?: afs_process_async_call);
| ^~~~~~~~~
Caused by commit
dabae7218d1c ("afs: Fix lock recursion")
I have used the vfs-brauner-fixes tree from next-20241016 for today. I
had to use the vfs-brauner tree from next-20241016 as well.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-10-17 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 1:46 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 12:17 linux-next: build failure after merge of the vfs-brauner-fixes tree Mark Brown
2026-04-23 11:52 Mark Brown
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=20241017124635.3298b1c4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brauner@kernel$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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