From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: linux-next: Tree for Dec 15 (fs/afs/)
Date: Fri, 15 Dec 2023 21:31:07 -0800 [thread overview]
Message-ID: <d9462e4d-5079-4f9a-9e50-bfa985381468@infradead.org> (raw)
In-Reply-To: <8a078303-f52b-4e3c-91da-315556e3738e@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 4403 bytes --]
(sorry, that didn't work)
On 12/15/23 21:29, Randy Dunlap wrote:
>
>
> On 12/14/23 20:01, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20231214:
>>
>
> on i386:
>
>
In file included from ../arch/x86/include/asm/atomic.h:8,
from ../include/linux/atomic.h:7,
from ../include/linux/jump_label.h:255,
from ../include/linux/static_key.h:1,
from ../arch/x86/include/asm/nospec-branch.h:6,
from ../arch/x86/include/asm/paravirt_types.h:11,
from ../arch/x86/include/asm/ptrace.h:97,
from ../arch/x86/include/asm/math_emu.h:5,
from ../arch/x86/include/asm/processor.h:13,
from ../arch/x86/include/asm/timex.h:5,
from ../include/linux/timex.h:67,
from ../include/linux/time32.h:13,
from ../include/linux/time.h:60,
from ../include/linux/stat.h:19,
from ../include/linux/module.h:13,
from ../fs/afs/callback.c:17:
../fs/afs/callback.c: In function '__afs_break_callback':
../arch/x86/include/asm/cmpxchg.h:67:25: error: call to '__xchg_wrong_size' declared with attribute error: Bad argument size for xchg
67 | __ ## op ## _wrong_size(); \
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../arch/x86/include/asm/cmpxchg.h:78:33: note: in expansion of macro '__xchg_op'
78 | #define arch_xchg(ptr, v) __xchg_op((ptr), (v), xchg, "")
| ^~~~~~~~~
../include/linux/atomic/atomic-arch-fallback.h:12:18: note: in expansion of macro 'arch_xchg'
12 | #define raw_xchg arch_xchg
| ^~~~~~~~~
../include/linux/atomic/atomic-instrumented.h:4716:9: note: in expansion of macro 'raw_xchg'
4716 | raw_xchg(__ai_ptr, __VA_ARGS__); \
| ^~~~~~~~
../fs/afs/callback.c:82:13: note: in expansion of macro 'xchg'
82 | if (xchg(&vnode->cb_expires_at, AFS_NO_CB_PROMISE) != AFS_NO_CB_PROMISE) {
| ^~~~
In file included from ../arch/x86/include/asm/atomic.h:8,
from ../include/linux/atomic.h:7,
from ../include/linux/jump_label.h:255,
from ../include/linux/static_key.h:1,
from ../arch/x86/include/asm/nospec-branch.h:6,
from ../arch/x86/include/asm/paravirt_types.h:11,
from ../arch/x86/include/asm/ptrace.h:97,
from ../arch/x86/include/asm/math_emu.h:5,
from ../arch/x86/include/asm/processor.h:13,
from ../arch/x86/include/asm/cpufeature.h:5,
from ../arch/x86/include/asm/thread_info.h:53,
from ../include/linux/thread_info.h:60,
from ../arch/x86/include/asm/preempt.h:9,
from ../include/linux/preempt.h:79,
from ../include/linux/spinlock.h:56,
from ../include/linux/mmzone.h:8,
from ../include/linux/gfp.h:7,
from ../include/linux/slab.h:16,
from ../fs/afs/rotate.c:9:
../fs/afs/rotate.c: In function 'afs_start_fs_iteration':
../arch/x86/include/asm/cmpxchg.h:67:25: error: call to '__xchg_wrong_size' declared with attribute error: Bad argument size for xchg
67 | __ ## op ## _wrong_size(); \
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../arch/x86/include/asm/cmpxchg.h:78:33: note: in expansion of macro '__xchg_op'
78 | #define arch_xchg(ptr, v) __xchg_op((ptr), (v), xchg, "")
| ^~~~~~~~~
../include/linux/atomic/atomic-arch-fallback.h:12:18: note: in expansion of macro 'arch_xchg'
12 | #define raw_xchg arch_xchg
| ^~~~~~~~~
../include/linux/atomic/atomic-instrumented.h:4716:9: note: in expansion of macro 'raw_xchg'
4716 | raw_xchg(__ai_ptr, __VA_ARGS__); \
| ^~~~~~~~
../fs/afs/rotate.c:102:21: note: in expansion of macro 'xchg'
102 | if (xchg(&vnode->cb_expires_at, AFS_NO_CB_PROMISE) != AFS_NO_CB_PROMISE)
| ^~~~
Full randconfig file is attached.
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
[-- Attachment #2: config-r3962.gz --]
[-- Type: application/gzip, Size: 33802 bytes --]
prev parent reply other threads:[~2023-12-16 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 4:01 linux-next: Tree for Dec 15 Stephen Rothwell
2023-12-16 5:26 ` linux-next: Tree for Dec 15 (drivers/net/ethernet/intel/ice/ice_base.c) Randy Dunlap
2023-12-18 17:29 ` Tony Nguyen
2023-12-16 5:29 ` linux-next: Tree for Dec 15 (fs/afs/) Randy Dunlap
2023-12-16 5:31 ` Randy Dunlap [this message]
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=d9462e4d-5079-4f9a-9e50-bfa985381468@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).