Re: linux-next: build failure after merge of the tip tree

Hi Sedat, On Sat, 27 Mar 2021 12:50:55 +0100 Sedat Dilek wrote: > > I wonder why Stephen's fixup-patch was not carried in recent > Linux-next releases. It is part of the tip tree merge commit. So it is not an explicit commit on its own, but the needed change is there. > Wild speculation - no

Re: linux-next: build failure after merge of the tip tree

On Fri, Mar 26, 2021 at 2:11 PM Borislav Petkov wrote: > > On Fri, Mar 26, 2021 at 09:57:43AM +0100, Sedat Dilek wrote: > > The commit b90829704780 "bpf: Use NOP_ATOMIC5 instead of > > emit_nops(, 5) for BPF_TRAMP_F_CALL_ORIG" is now in Linus Git > > (see [1]). > > > > Where will Stephen's

Re: linux-next: build failure after merge of the tip tree

On Fri, Mar 26, 2021 at 09:57:43AM +0100, Sedat Dilek wrote: > The commit b90829704780 "bpf: Use NOP_ATOMIC5 instead of > emit_nops(, 5) for BPF_TRAMP_F_CALL_ORIG" is now in Linus Git > (see [1]). > > Where will Stephen's fixup-patch be carried? > Linux-next? > net-next? > ? I guess we'll

Re: linux-next: build failure after merge of the tip tree

On Mon, Mar 22, 2021 at 10:02 AM Borislav Petkov wrote: > > On Mon, Mar 22, 2021 at 02:37:14PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > arch/x86/net/bpf_jit_comp.c: In function

Re: linux-next: build failure after merge of the tip tree

On Mon, Mar 22, 2021 at 4:39 AM Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > arch/x86/net/bpf_jit_comp.c: In function 'arch_prepare_bpf_trampoline': > arch/x86/net/bpf_jit_comp.c:2015:16: error:

Re: linux-next: build failure after merge of the tip tree

On Mon, Mar 22, 2021 at 02:37:14PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > arch/x86/net/bpf_jit_comp.c: In function 'arch_prepare_bpf_trampoline': > arch/x86/net/bpf_jit_comp.c:2015:16: error:

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/net/bpf_jit_comp.c: In function 'arch_prepare_bpf_trampoline': arch/x86/net/bpf_jit_comp.c:2015:16: error: 'ideal_nops' undeclared (first use in this function) 2015 | memcpy(prog,

Re: linux-next: build failure after merge of the tip tree

Hi Ingo, On Wed, 17 Mar 2021 21:04:08 +0100 Ingo Molnar wrote: > > * Borislav Petkov wrote: > > > On Thu, Mar 18, 2021 at 05:49:21AM +1100, Stephen Rothwell wrote: > > > That fixes the powerpc build for me, thanks. > > > > Thx, adding your Tested-by and pushing out. > > I've pushed

Re: linux-next: build failure after merge of the tip tree

* Borislav Petkov wrote: > On Thu, Mar 18, 2021 at 05:49:21AM +1100, Stephen Rothwell wrote: > > That fixes the powerpc build for me, thanks. > > Thx, adding your Tested-by and pushing out. I've pushed this out into tip:auto-latest as well, so that tomorrow's -next should pick this up

Re: linux-next: build failure after merge of the tip tree

On Thu, Mar 18, 2021 at 05:49:21AM +1100, Stephen Rothwell wrote: > That fixes the powerpc build for me, thanks. Thx, adding your Tested-by and pushing out. -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

Re: linux-next: build failure after merge of the tip tree

Hi Borislav, On Wed, 17 Mar 2021 19:02:36 +0100 Borislav Petkov wrote: > > On Wed, Mar 17, 2021 at 09:22:15AM -0700, Ian Rogers wrote: > > The path also needs fixing. With the following > > I was able to build for arm64 and powerpc. > > Thanks, I've updated and added your Tested-by. I'll

Re: linux-next: build failure after merge of the tip tree

On Wed, Mar 17, 2021 at 09:22:15AM -0700, Ian Rogers wrote: > The path also needs fixing. With the following > I was able to build for arm64 and powerpc. Thanks, I've updated and added your Tested-by. I'll give sfr a chance to test and queue it tomorrow. --- >From

Re: linux-next: build failure after merge of the tip tree

On Wed, Mar 17, 2021 at 3:54 AM Borislav Petkov wrote: > > + Ian. > > On Wed, Mar 17, 2021 at 03:08:58PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (native perf) > > failed like this: > > > > In file included from

Re: linux-next: build failure after merge of the tip tree

+ Ian. On Wed, Mar 17, 2021 at 03:08:58PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (native perf) > failed like this: > > In file included from util/intel-pt-decoder/intel-pt-insn-decoder.c:15: >

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (native perf) failed like this: In file included from util/intel-pt-decoder/intel-pt-insn-decoder.c:15: util/intel-pt-decoder/../../../arch/x86/lib/insn.c:14:10: fatal error: asm/inat.h: No such file or directory 14 | #include

Re: linux-next: build failure after merge of the tip tree

Hi Peter, On Wed, 3 Mar 2021 10:44:32 +0100 Peter Zijlstra wrote: > > Damn, sorry about that. I've rebased tip/sched/core and all should be > well now. Excellent, thanks. -- Cheers, Stephen Rothwell pgpxZzQ5s2EcR.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the tip tree

On Wed, Mar 03, 2021 at 10:38:42AM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from drivers/usb/usbip/usbip_common.c:18: > drivers/usb/usbip/usbip_common.h: In function

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/usb/usbip/usbip_common.c:18: drivers/usb/usbip/usbip_common.h: In function 'usbip_kcov_handle_init': drivers/usb/usbip/usbip_common.h:348:20: error: implicit

Re: linux-next: build failure after merge of the tip tree

On Thu, Jan 14, 2021 at 03:11:45PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > arch/x86/kernel/cpu/amd.c: In function 'bsp_init_amd': > arch/x86/kernel/cpu/amd.c:545:3: error:

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) failed like this: arch/x86/kernel/cpu/amd.c: In function 'bsp_init_amd': arch/x86/kernel/cpu/amd.c:545:3: error: '__max_die_per_package' undeclared (first use in this function); did you mean

Re: linux-next: build failure after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > kernel/smp.c: In function 'csd_lock_wait_getcpu': > kernel/smp.c:133:13: error: 'call_single_data_t' {aka 'struct > __call_single_data'} has no member

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: kernel/smp.c: In function 'csd_lock_wait_getcpu': kernel/smp.c:133:13: error: 'call_single_data_t' {aka 'struct __call_single_data'} has no member named 'dst' 133 | return csd->dst; /* Other

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/thread_info.h:38, from arch/x86/include/asm/preempt.h:7, from include/linux/preempt.h:78, from

Re: linux-next: build failure after merge of the tip tree

On Fri, Oct 09, 2020 at 03:28:46PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (perf) failed > like this: > > In file included from tools/include/linux/build_bug.h:5, > from tools/include/linux/kernel.h:8, >

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (perf) failed like this: In file included from tools/include/linux/build_bug.h:5, from tools/include/linux/kernel.h:8, from util/intel-pt-decoder/intel-pt-insn-decoder.c:7:

Re: linux-next: build failure after merge of the tip tree

On Tue, Sep 08, 2020 at 07:12:23PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > ERROR: modpost: too long symbol > ".__tracepoint_iter_pnfs_mds_fallback_pg_get_mirror_count" >

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc allyesconfig) failed like this: ERROR: modpost: too long symbol ".__tracepoint_iter_pnfs_mds_fallback_pg_get_mirror_count" [fs/nfs/flexfilelayout/nfs_layout_flexfiles.ko] Caused by commit d25e37d89dd2 ("tracepoint:

Re: linux-next: build failure after merge of the tip tree

Hi Ingo, On Thu, 3 Sep 2020 05:51:08 +0200 Ingo Molnar wrote: > > I've merged the old commit by mistake - it's removed now. Ah, OK, thanks. -- Cheers, Stephen Rothwell pgpqbzuw8G3mY.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > > Caused by commit > > f670269a42bf ("x86: Fix early boot crash on gcc-10, next try") > > interacting with commit > > a9a3ed1eff36 ("x86: Fix

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: Caused by commit f670269a42bf ("x86: Fix early boot crash on gcc-10, next try") interacting with commit a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10, third try") from Linus'

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: modpost: "sched_setscheduler" [drivers/gpu/drm/drm.ko] undefined! Caused by commit 616d91b68cd5 ("sched: Remove sched_setscheduler*() EXPORTs") interacting with commit 5e6c2b4f9161

Re: linux-next: build failure after merge of the tip tree

Hi Ingo, On Fri, 31 Jul 2020 11:57:35 +0200 Ingo Molnar wrote: > > I've merged Linus's latest into tip:locking/core, keeping the simpler > solution of a6342915881a and reducing the dependency hell. > > Will push it all out hopefully later today (unrelated changes need > more testing), from

Re: linux-next: build failure after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from include/asm-generic/getorder.h:8, > from arch/arm/include/asm/page.h:166, > from

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/asm-generic/getorder.h:8, from arch/arm/include/asm/page.h:166, from arch/arm/include/asm/thread_info.h:14,

Re: linux-next: build failure after merge of the tip tree

Hi all, On Tue, 14 Jul 2020 13:50:12 +1000 Stephen Rothwell wrote: > > On Tue, 7 Jul 2020 12:33:01 +1000 Stephen Rothwell > wrote: > > > > On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell > > wrote: > > > > > > On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell > > > wrote: > >

Re: linux-next: build failure after merge of the tip tree

Hi all, On Tue, 7 Jul 2020 12:33:01 +1000 Stephen Rothwell wrote: > > On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell > wrote: > > > > On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell > > wrote: > > > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)

Re: linux-next: build failure after merge of the tip tree

Hi all, On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell wrote: > > On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell > wrote: > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > ERROR: modpost: "sched_setscheduler" > >

Re: linux-next: build failure after merge of the tip tree

Hi all, On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: modpost: "sched_setscheduler" [kernel/trace/ring_buffer_benchmark.ko] > undefined! > > Caused by commit > >

Re: linux-next: build failure after merge of the tip tree

Hi Borislav, On Sun, 21 Jun 2020 12:53:50 +0200 Borislav Petkov wrote: > > + acme for an FYI. > > On Sun, Jun 21, 2020 at 04:33:23PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (perf) failed > > like this: > > > > In file included

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: modpost: "sched_setscheduler" [kernel/trace/ring_buffer_benchmark.ko] undefined! Caused by commit 616d91b68cd5 ("sched: Remove sched_setscheduler*() EXPORTs") Missed one :-) I have

Re: linux-next: build failure after merge of the tip tree

+ acme for an FYI. On Sun, Jun 21, 2020 at 04:33:23PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (perf) failed > like this: > > In file included from trace/beauty/tracepoints/x86_msr.c:10: >

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (perf) failed like this: In file included from trace/beauty/tracepoints/x86_msr.c:10: perf/trace/beauty/generated/x86_arch_MSRs_array.c:292:45: error: initialized field overwritten [-Werror=override-init] 292 | [0xc0010280 -

Re: linux-next: build failure after merge of the tip tree

On Mon, May 25, 2020 at 10:20:29AM +0200, Marco Elver wrote: > On Mon, 25 May 2020 at 02:37, Paul E. McKenney wrote: > > > > On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote: > > > On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote: > > > > "Paul E. McKenney" writes:

Re: linux-next: build failure after merge of the tip tree

On Mon, 25 May 2020 at 02:37, Paul E. McKenney wrote: > > On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote: > > On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote: > > > "Paul E. McKenney" writes: > > > > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner

Re: linux-next: build failure after merge of the tip tree

On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote: > On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote: > > "Paul E. McKenney" writes: > > > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote: > > >> core/rcu is the one which diverged and caused the merge

Re: linux-next: build failure after merge of the tip tree

On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote: > "Paul E. McKenney" writes: > > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote: > >> core/rcu is the one which diverged and caused the merge conflict with > >> PPC to happen twice. So Paul needs to remove the stale

Re: linux-next: build failure after merge of the tip tree

"Paul E. McKenney" writes: > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote: >> core/rcu is the one which diverged and caused the merge conflict with >> PPC to happen twice. So Paul needs to remove the stale core/rcu bits and >> rebase on the current version (which is not going

Re: linux-next: build failure after merge of the tip tree

On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote: > Borislav Petkov writes: > > > On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote: > >> Marco, Thomas, is there any better setup I can provide Stephen? Or > >> is the next-20200519 -rcu tree the best we have right

Re: linux-next: build failure after merge of the tip tree

Borislav Petkov writes: > On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote: >> Marco, Thomas, is there any better setup I can provide Stephen? Or >> is the next-20200519 -rcu tree the best we have right now? > > I've queued the fixes yesterday into tip:locking/kcsan and tglx

Re: linux-next: build failure after merge of the tip tree

On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote: > Marco, Thomas, is there any better setup I can provide Stephen? Or > is the next-20200519 -rcu tree the best we have right now? I've queued the fixes yesterday into tip:locking/kcsan and tglx said something about you having to

Re: linux-next: build failure after merge of the tip tree

On Fri, May 22, 2020 at 05:49:44PM +1000, Stephen Rothwell wrote: > Hi all, > > On Fri, 22 May 2020 17:17:08 +1000 Stephen Rothwell > wrote: > > > > On Thu, 21 May 2020 18:35:22 +0100 Will Deacon wrote: > > > > > > [+Marco and Boris] > > > > > > On Fri, May 22, 2020 at 03:31:19AM +1000,

Re: linux-next: build failure after merge of the tip tree

Hi all, On Fri, 22 May 2020 17:17:08 +1000 Stephen Rothwell wrote: > > On Thu, 21 May 2020 18:35:22 +0100 Will Deacon wrote: > > > > [+Marco and Boris] > > > > On Fri, May 22, 2020 at 03:31:19AM +1000, Stephen Rothwell wrote: > > > After merging the tip tree, all my linux-next builds took

Re: linux-next: build failure after merge of the tip tree

Hi Will, On Thu, 21 May 2020 18:35:22 +0100 Will Deacon wrote: > > [+Marco and Boris] > > On Fri, May 22, 2020 at 03:31:19AM +1000, Stephen Rothwell wrote: > > After merging the tip tree, all my linux-next builds took signficantly > > longer and used much more memory. In some cases, builds

Re: linux-next: build failure after merge of the tip tree

Hi Stephen, [+Marco and Boris] On Fri, May 22, 2020 at 03:31:19AM +1000, Stephen Rothwell wrote: > After merging the tip tree, all my linux-next builds took signficantly > longer and used much more memory. In some cases, builds would seg fault > due to running out of memory :-( > > I have

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, all my linux-next builds took signficantly longer and used much more memory. In some cases, builds would seg fault due to running out of memory :-( I have eventaully bisected it to commit cdd28ad2d811 ("READ_ONCE: Use data_race() to avoid KCSAN

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/kernel/ftrace.c: In function 'set_ftrace_ops_ro': arch/x86/kernel/ftrace.c:444:32: error: 'ftrace_epilogue' undeclared (first use in this function) 444 |end_offset = (unsigned

Re: linux-next: build failure after merge of the tip tree

Hi Ingo, On Mon, 21 Oct 2019 07:51:41 +0200 Ingo Molnar wrote: > > Hm, that was a weird merge mishap - sorry about that, should go away in > the next -next iteration. Thanks. -- Cheers, Stephen Rothwell pgp3bI3wEmsAy.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (native perf) > failed like this: > > make: execvp: ./check-headers.sh: Permission denied > > Caused by commit > > 05f2f277053d ("Merge branch 'x86/core'") > > which somehow removed execute

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (native perf) failed like this: make: execvp: ./check-headers.sh: Permission denied Caused by commit 05f2f277053d ("Merge branch 'x86/core'") which somehow removed execute permissions from tools/perf/check-headers.sh I added a

Re: linux-next: build failure after merge of the tip tree

On Thu, Oct 10, 2019 at 10:23:21PM +1100, Stephen Rothwell wrote: > Hi Ingo, > > On Thu, 10 Oct 2019 10:02:07 +0200 Ingo Molnar wrote: > > > > I suspect -next will have to carry this semantic merge conflict > > resolution until the DRM tree is merged upstream. > > Yep, its not a real problem,

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/i915/gt/intel_gt_pm.c: In function 'intel_gt_resume': drivers/gpu/drm/i915/gt/intel_gt_pm.c:183:54: error: macro "mutex_release" passed 3 arguments, but takes just 2 183 |

Re: linux-next: build failure after merge of the tip tree

On Thu, Aug 29, 2019 at 02:24:24PM +0200, Thomas Gleixner wrote: > On Thu, 29 Aug 2019, Peter Zijlstra wrote: > > On Thu, Aug 29, 2019 at 04:20:12PM +1000, Stephen Rothwell wrote: > > > From: Stephen Rothwell > > > Date: Thu, 29 Aug 2019 16:08:49 +1000 > > > Subject: [PATCH] ASoC: Intel: boards:

Re: linux-next: build failure after merge of the tip tree

On Thu, 29 Aug 2019, Peter Zijlstra wrote: > On Thu, Aug 29, 2019 at 04:20:12PM +1000, Stephen Rothwell wrote: > > From: Stephen Rothwell > > Date: Thu, 29 Aug 2019 16:08:49 +1000 > > Subject: [PATCH] ASoC: Intel: boards: merge fix for > > INTEL_FAM6_KABYLAKE_MOBILE -> INTEL_FAM6_KABYLAKE_L

Re: linux-next: build failure after merge of the tip tree

On Thu, Aug 29, 2019 at 04:20:12PM +1000, Stephen Rothwell wrote: > From: Stephen Rothwell > Date: Thu, 29 Aug 2019 16:08:49 +1000 > Subject: [PATCH] ASoC: Intel: boards: merge fix for > INTEL_FAM6_KABYLAKE_MOBILE -> INTEL_FAM6_KABYLAKE_L change > > Signed-off-by: Stephen Rothwell > --- >

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from sound/soc/intel/boards/sof_rt5682.c:23: sound/soc/intel/boards/../common/soc-intel-quirks.h: In function 'soc_intel_is_cml':

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/locking/mutex-debug.c: In function 'debug_mutex_lock_common': kernel/locking/mutex-debug.c:32:42: error: dereferencing pointer to incomplete type 'struct mutex_waiter'

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/android/vsoc.c: In function 'handle_vsoc_cond_wait': drivers/staging/android/vsoc.c:440:33: error: passing argument 1 of 'hrtimer_init_sleeper_on_stack' from incompatible pointer

Re: linux-next: build failure after merge of the tip tree

Hi Ilya, On Wed, 10 Jul 2019 20:21:33 +0200 Ilya Dryomov wrote: > > Yes, that is what I figured would happen. I assume you would keep > carrying this fixup until the ceph tree is merged. Of course. -- Cheers, Stephen Rothwell pgp3xqEtkmhJC.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the tip tree

On Wed, Jul 10, 2019 at 2:01 AM Stephen Rothwell wrote: > > Hi all, > > On Tue, 9 Jul 2019 16:54:59 +1000 Stephen Rothwell > wrote: > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > drivers/block/rbd.c: In function

Re: linux-next: build failure after merge of the tip tree

Hi all, On Tue, 9 Jul 2019 16:54:59 +1000 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/block/rbd.c: In function 'wake_lock_waiters': > drivers/block/rbd.c:3933:2: error: implicit declaration of function

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/block/rbd.c: In function 'wake_lock_waiters': drivers/block/rbd.c:3933:2: error: implicit declaration of function 'lockdep_assert_held_exclusive'; did you mean

Re: linux-next: build failure after merge of the tip tree

Hi all, On Tue, 25 Jun 2019 16:04:32 +1000 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data': > drivers/net/wireless/intersil/p54/txrx.c:386:28:

Re: linux-next: build failure after merge of the tip tree

Hi all, On Tue, 25 Jun 2019 16:04:32 +1000 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data': > drivers/net/wireless/intersil/p54/txrx.c:386:28:

Re: linux-next: build failure after merge of the tip tree

Hi David, On Tue, 2 Jul 2019 12:28:32 +0200 David Sterba wrote: > > On Tue, Jul 02, 2019 at 03:33:02PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > fs/btrfs/ctree.c: In function

Re: linux-next: build failure after merge of the tip tree

Hi David, On Tue, 2 Jul 2019 12:28:32 +0200 David Sterba wrote: > > I can move the patches out of the for-5.3 branch and send them > separately after the rename gets merged, they're merely adding the > assertion and otherwise do not affect the rest of the code. > > Fixing that in another way

Re: linux-next: build failure after merge of the tip tree

On Tue, Jul 02, 2019 at 03:33:02PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > fs/btrfs/ctree.c: In function '__tree_mod_log_insert': > fs/btrfs/ctree.c:388:2: error: implicit declaration of

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: fs/btrfs/ctree.c: In function '__tree_mod_log_insert': fs/btrfs/ctree.c:388:2: error: implicit declaration of function 'lockdep_assert_held_exclusive'; did you mean

Re: linux-next: build failure after merge of the tip tree

Thomas Gleixner writes: > On Tue, 25 Jun 2019, Stephen Rothwell wrote: > >> Hi Kalle, >> >> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote: >> > >> > Thanks for the report. Any suggestions how to handle this? Or do we let >> > Linus take care of this? >> >> Just let Linus take care of it

Re: linux-next: build failure after merge of the tip tree

On Tue, 25 Jun 2019, Stephen Rothwell wrote: > Hi Kalle, > > On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote: > > > > Thanks for the report. Any suggestions how to handle this? Or do we let > > Linus take care of this? > > Just let Linus take care of it ... mention it in the pull request

Re: linux-next: build failure after merge of the tip tree

Stephen Rothwell writes: > On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote: >> >> Thanks for the report. Any suggestions how to handle this? Or do we let >> Linus take care of this? > > Just let Linus take care of it ... mention it in the pull request ... Thanks, I'll do that. > I guess

Re: linux-next: build failure after merge of the tip tree

Hi Kalle, On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote: > > Thanks for the report. Any suggestions how to handle this? Or do we let > Linus take care of this? Just let Linus take care of it ... mention it in the pull request ... I guess DaveM needs to know, right? -- Cheers, Stephen

Re: linux-next: build failure after merge of the tip tree

On Tue, 25 Jun 2019, Kalle Valo wrote: > Stephen Rothwell writes: > > --- > > drivers/net/wireless/intersil/p54/txrx.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/drivers/net/wireless/intersil/p54/txrx.c > > b/drivers/net/wireless/intersil/p54/txrx.c > > index

Re: linux-next: build failure after merge of the tip tree

Stephen Rothwell writes: > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data': > drivers/net/wireless/intersil/p54/txrx.c:386:28: error: implicit declaration > of function

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data': drivers/net/wireless/intersil/p54/txrx.c:386:28: error: implicit declaration of function 'ktime_get_boot_ns'; did you mean

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: /bin/bash: scripts/atomic/check-atomics.sh: No such file or directory Caused by commit 8d32588077bd ("locking/atomics: Check generated headers are up-to-date") I build with O= I have

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: /bin/bash: scripts/atomic/check-atomics.sh: No such file or directory Caused by commit 8d32588077bd ("locking/atomics: Check generated headers are up-to-date") I build with O= I have

Re: linux-next: build failure after merge of the tip tree

Hi Stephen, On Thu, Aug 09, 2018 at 09:24:20AM +1000, Stephen Rothwell wrote: > Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned > /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target > 'arch/x86/boot/compressed/vmlinux.relocs' failed > > Caused by commit > >

Re: linux-next: build failure after merge of the tip tree

Hi Stephen, On Thu, Aug 09, 2018 at 09:24:20AM +1000, Stephen Rothwell wrote: > Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned > /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target > 'arch/x86/boot/compressed/vmlinux.relocs' failed > > Caused by commit > >

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 defconfig) failed like this: Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target 'arch/x86/boot/compressed/vmlinux.relocs' failed Caused by

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 defconfig) failed like this: Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target 'arch/x86/boot/compressed/vmlinux.relocs' failed Caused by

Re: linux-next: build failure after merge of the tip tree

On Tue, Apr 03, 2018 at 01:39:08PM +0100, David Howells wrote: > Peter Zijlstra wrote: > > > I figured that since there were only a handful of users it wasn't a > > popular API, also David very much knew of those patches changing it so > > could easily have pulled in the

Re: linux-next: build failure after merge of the tip tree

On Tue, Apr 03, 2018 at 01:39:08PM +0100, David Howells wrote: > Peter Zijlstra wrote: > > > I figured that since there were only a handful of users it wasn't a > > popular API, also David very much knew of those patches changing it so > > could easily have pulled in the special tip/sched/wait

Re: linux-next: build failure after merge of the tip tree

Stephen Rothwell wrote: > + wait_var_event(>nr_calls, !atomic_read(>nr_calls)); I would prefer == 0 to ! as it's not really a true/false value. But apart from that, it's looks okay and you can add my Reviewed-by. David

Re: linux-next: build failure after merge of the tip tree

Stephen Rothwell wrote: > + wait_var_event(>nr_calls, !atomic_read(>nr_calls)); I would prefer == 0 to ! as it's not really a true/false value. But apart from that, it's looks okay and you can add my Reviewed-by. David

Re: linux-next: build failure after merge of the tip tree

Peter Zijlstra wrote: > I figured that since there were only a handful of users it wasn't a > popular API, also David very much knew of those patches changing it so > could easily have pulled in the special tip/sched/wait branch :/ I'm not sure I could, since I have to

Re: linux-next: build failure after merge of the tip tree

Peter Zijlstra wrote: > I figured that since there were only a handful of users it wasn't a > popular API, also David very much knew of those patches changing it so > could easily have pulled in the special tip/sched/wait branch :/ I'm not sure I could, since I have to base on net-next. I'm

Re: linux-next: build failure after merge of the tip tree

On Tue, Apr 03, 2018 at 03:41:22PM +1000, Stephen Rothwell wrote: > Caused by commit > > 9b8cce52c4b5 ("sched/wait: Remove the wait_on_atomic_t() API") > > interacting with commits > > d3be4d244330 ("xrpc: Fix potential call vs socket/net destruction race") > 31f5f9a1691e ("rxrpc: Fix

Re: linux-next: build failure after merge of the tip tree

On Tue, Apr 03, 2018 at 03:41:22PM +1000, Stephen Rothwell wrote: > Caused by commit > > 9b8cce52c4b5 ("sched/wait: Remove the wait_on_atomic_t() API") > > interacting with commits > > d3be4d244330 ("xrpc: Fix potential call vs socket/net destruction race") > 31f5f9a1691e ("rxrpc: Fix

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: net/rxrpc/call_object.c: In function 'rxrpc_rcu_destroy_call': net/rxrpc/call_object.c:661:3: error: implicit declaration of function 'wake_up_atomic_t'; did you mean 'wake_up_bit'?

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: net/rxrpc/call_object.c: In function 'rxrpc_rcu_destroy_call': net/rxrpc/call_object.c:661:3: error: implicit declaration of function 'wake_up_atomic_t'; did you mean 'wake_up_bit'?

  1   2   3   4   5   >