public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: 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 header_cleanup tree
Date: Mon, 18 Dec 2023 17:29:35 +1100	[thread overview]
Message-ID: <20231218172935.0730d54c@canb.auug.org.au> (raw)

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

Hi all,

After merging the header_cleanup tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

In file included from include/linux/uaccess.h:12,
                 from include/linux/uio.h:9,
                 from include/linux/socket.h:8,
                 from include/linux/compat.h:15,
                 from arch/powerpc/kernel/asm-offsets.c:12:
arch/powerpc/include/asm/uaccess.h: In function 'copy_mc_to_user':
arch/powerpc/include/asm/uaccess.h:374:13: error: implicit declaration of function 'check_copy_size' [-Werror=implicit-function-declaration]
  374 |         if (check_copy_size(from, n, true)) {
      |             ^~~~~~~~~~~~~~~
include/linux/uaccess.h: At top level:
include/linux/uaccess.h:66:1: error: conflicting types for 'check_copy_size'; have 'bool(const void *, size_t,  bool)' {aka '_Bool(const void *, long unsigned int,  _Bool)'}
   66 | check_copy_size(const void *addr, size_t bytes, bool is_source)
      | ^~~~~~~~~~~~~~~
arch/powerpc/include/asm/uaccess.h:374:13: note: previous implicit declaration of 'check_copy_size' with type 'int()'
  374 |         if (check_copy_size(from, n, true)) {
      |             ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors

Caused/exposed by commit

  f95cbe69154f ("thread_info, uaccess.h: Move HARDENED_USERCOPY to better location")

I have reverted that commit for today.

I then got this:

arch/powerpc/kvm/book3s_64_vio.c: In function 'kvm_spapr_tce_release_iommu_group':
arch/powerpc/kvm/book3s_64_vio.c:103:17: error: implicit declaration of function 'cond_resched_rcu'; did you mean 'cond_resched_lock'? [-Werror=implicit-function-declaration]
  103 |                 cond_resched_rcu();
      |                 ^~~~~~~~~~~~~~~~
      |                 cond_resched_lock
cc1: all warnings being treated as errors

and this:

arch/powerpc/kernel/interrupt.c: In function 'syscall_exit_prepare':
arch/powerpc/kernel/interrupt.c:275:9: error: implicit declaration of function 'rseq_syscall'; did you mean 'si_syscall'? [-Werror=implicit-function-declaration]
  275 |         rseq_syscall(regs);
      |         ^~~~~~~~~~~~ 
      |         si_syscall   
cc1: all warnings being treated as errors

For which I applied this:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 18 Dec 2023 17:26:13 +1100
Subject: [PATCH] fix up for some header_claenup patches

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/powerpc/kernel/interrupt.c  | 1 +
 arch/powerpc/kvm/book3s_64_vio.c | 1 +
 2 files changed, 2 insertions(+)

diff --git a/arch/powerpc/kernel/interrupt.c b/arch/powerpc/kernel/interrupt.c
index c4f6d3c69ba9..94e9e2cdc557 100644
--- a/arch/powerpc/kernel/interrupt.c
+++ b/arch/powerpc/kernel/interrupt.c
@@ -4,6 +4,7 @@
 #include <linux/err.h>
 #include <linux/compat.h>
 #include <linux/sched/debug.h> /* for show_regs */
+#include <linux/rseq.h>
 
 #include <asm/kup.h>
 #include <asm/cputime.h>
diff --git a/arch/powerpc/kvm/book3s_64_vio.c b/arch/powerpc/kvm/book3s_64_vio.c
index 14c6d7e318da..b569ebaa590e 100644
--- a/arch/powerpc/kvm/book3s_64_vio.c
+++ b/arch/powerpc/kvm/book3s_64_vio.c
@@ -20,6 +20,7 @@
 #include <linux/iommu.h>
 #include <linux/file.h>
 #include <linux/mm.h>
+#include <linux/rcupdate_wait.h>
 
 #include <asm/kvm_ppc.h>
 #include <asm/kvm_book3s.h>
-- 
2.40.1

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-12-18  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18  6:29 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18  6:40 linux-next: build failure after merge of the header_cleanup tree Stephen Rothwell
2023-12-19  3:57 ` Stephen Rothwell
2023-12-19 13:53   ` Ville Syrjälä
2023-12-19  4:25 Stephen Rothwell
2023-12-19  4:59 ` Kent Overstreet

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=20231218172935.0730d54c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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