Re: [locking/ww_mutex] 2a0c112828 WARNING: CPU: 0 PID: 18 at kernel/locking/mutex.c:305 __ww_mutex_wakeup_for_backoff

1:40:43PM +0800, Fengguang Wu wrote: > > > Thanks for the patch! I applied the patch on top of "locking/ww_mutex: > > > Add kselftests for ww_mutex stress", and find no "bad unlock balance > > > detected" but this warning. Attached is the new dmesg w

Re: [locking/ww_mutex] 2a0c112828 WARNING: CPU: 0 PID: 18 at kernel/locking/mutex.c:305 __ww_mutex_wakeup_for_backoff

1:40:43PM +0800, Fengguang Wu wrote: > > > Thanks for the patch! I applied the patch on top of "locking/ww_mutex: > > > Add kselftests for ww_mutex stress", and find no "bad unlock balance > > > detected" but this warning. Attached is the new dmesg w

Re: [locking/ww_mutex] 2a0c112828 WARNING: CPU: 0 PID: 18 at kernel/locking/mutex.c:305 __ww_mutex_wakeup_for_backoff

On Wed, Mar 01, 2017 at 04:51:36PM +0100, Peter Zijlstra wrote: On Wed, Mar 01, 2017 at 11:40:43PM +0800, Fengguang Wu wrote: Thanks for the patch! I applied the patch on top of "locking/ww_mutex: Add kselftests for ww_mutex stress", and find no "bad unlock balance detected&qu

Re: [locking/ww_mutex] 2a0c112828 WARNING: CPU: 0 PID: 18 at kernel/locking/mutex.c:305 __ww_mutex_wakeup_for_backoff

On Wed, Mar 01, 2017 at 04:51:36PM +0100, Peter Zijlstra wrote: On Wed, Mar 01, 2017 at 11:40:43PM +0800, Fengguang Wu wrote: Thanks for the patch! I applied the patch on top of "locking/ww_mutex: Add kselftests for ww_mutex stress", and find no "bad unlock balance detected&qu

Re: [bpf] 9d876e79df: BUG: unable to handle kernel paging request at 653a8346

[remove unrelated mailing lists] On Mon, Feb 27, 2017 at 04:25:57PM +0100, Daniel Borkmann wrote: >On 02/27/2017 03:14 AM, kernel test robot wrote: >> Greetings, >> >> 0day kernel testing robot got the below dmesg and the first bad commit is >> >>

Re: [bpf] 9d876e79df: BUG: unable to handle kernel paging request at 653a8346

[remove unrelated mailing lists] On Mon, Feb 27, 2017 at 04:25:57PM +0100, Daniel Borkmann wrote: >On 02/27/2017 03:14 AM, kernel test robot wrote: >> Greetings, >> >> 0day kernel testing robot got the below dmesg and the first bad commit is >> >>

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

The dummy_udc WARN is gone with this patch for 100+ times of boot tests. Tested-by: Xiaolong Ye Thanks, Xiaolong Thanks, Xiaolong. I will submit a patch for it. Thank you Peter! We've been noised by this warning for quite some time. Fengguang

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

The dummy_udc WARN is gone with this patch for 100+ times of boot tests. Tested-by: Xiaolong Ye Thanks, Xiaolong Thanks, Xiaolong. I will submit a patch for it. Thank you Peter! We've been noised by this warning for quite some time. Fengguang

Re: 289b7bfd48 BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff880012049289

On Tue, Feb 28, 2017 at 12:24:03PM +0800, Fengguang Wu wrote: Hi Linus Walleij, I'm not sure if this is a good bisect since the merged gpio branch suffers from another early hang problem which could hide the KASAN BUG. So also OF people are also included in the loop. The attached reproduce

Re: 289b7bfd48 BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff880012049289

On Tue, Feb 28, 2017 at 12:24:03PM +0800, Fengguang Wu wrote: Hi Linus Walleij, I'm not sure if this is a good bisect since the merged gpio branch suffers from another early hang problem which could hide the KASAN BUG. So also OF people are also included in the loop. The attached reproduce

[locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock

Hello, Here is another bisect result with a different call trace. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit f2a5fec17395f259d54daa8833d81b00cceb15c3 Author: Chris Wilson AuthorDate: Thu Dec 1 11:47:06 2016 + Commit:

[locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock

Hello, Here is another bisect result with a different call trace. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit f2a5fec17395f259d54daa8833d81b00cceb15c3 Author: Chris Wilson AuthorDate: Thu Dec 1 11:47:06 2016 + Commit: Ingo Molnar CommitDate:

[mm/kasan] 80a9201a59 BUG: kernel reboot-without-warning in early-boot stage, last printk: Booting the kernel.

Hi Alexander, FYI, we find an old bug that's still alive in linux-next. The attached reproduce-* script may help debug the problem. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 80a9201a5965f4715d5c09790862e0df84ce0614 Author: Alexander Potapenko

[mm/kasan] 80a9201a59 BUG: kernel reboot-without-warning in early-boot stage, last printk: Booting the kernel.

Hi Alexander, FYI, we find an old bug that's still alive in linux-next. The attached reproduce-* script may help debug the problem. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 80a9201a5965f4715d5c09790862e0df84ce0614 Author: Alexander Potapenko

Re: [platform/x86] 84c2f235ad BUG: KASAN: null-ptr-deref on address 0000000000000008

On Mon, Feb 27, 2017 at 03:53:56PM +1030, Jonathan Woithe wrote: On Mon, Feb 27, 2017 at 12:58:40PM +0800, Fengguang Wu wrote: Here is another bisect result. The attached reproduce-* script may help debug the issue. Thanks for this. FYI the cause of this issue is already understood (refer

Re: [platform/x86] 84c2f235ad BUG: KASAN: null-ptr-deref on address 0000000000000008

On Mon, Feb 27, 2017 at 03:53:56PM +1030, Jonathan Woithe wrote: On Mon, Feb 27, 2017 at 12:58:40PM +0800, Fengguang Wu wrote: Here is another bisect result. The attached reproduce-* script may help debug the issue. Thanks for this. FYI the cause of this issue is already understood (refer

[platform/x86] 84c2f235ad BUG: KASAN: null-ptr-deref on address 0000000000000008

Hi Alan, Here is another bisect result. The attached reproduce-* script may help debug the issue. git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git testing commit 84c2f235ad130cf59911fdd1970d297d28540d35 Author: Alan Jenkins AuthorDate: Wed

[platform/x86] 84c2f235ad BUG: KASAN: null-ptr-deref on address 0000000000000008

Hi Alan, Here is another bisect result. The attached reproduce-* script may help debug the issue. git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git testing commit 84c2f235ad130cf59911fdd1970d297d28540d35 Author: Alan Jenkins AuthorDate: Wed Feb 8 14:46:31 2017 +0100

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

[Sorry, resend to correct Felipe's email address] Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them.

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

[Sorry, resend to correct Felipe's email address] Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them.

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

Re: [Merge branch 'core-debugobjects-for-linus' of git] 575260e3f8: WARNING: CPU: 0 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

Hi Linus, On Fri, Feb 24, 2017 at 02:37:04PM -0800, Linus Torvalds wrote: This looks like two -tip trees together show some issue - the timer updates from Thomas triggering a debugobjects check from Ingo, thus fingering my merge as the culprit. Added Thomas/Ingo to the cc, leaving everything

Re: [Merge branch 'core-debugobjects-for-linus' of git] 575260e3f8: WARNING: CPU: 0 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

Hi Linus, On Fri, Feb 24, 2017 at 02:37:04PM -0800, Linus Torvalds wrote: This looks like two -tip trees together show some issue - the timer updates from Thomas triggering a debugobjects check from Ingo, thus fingering my merge as the culprit. Added Thomas/Ingo to the cc, leaving everything

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

On Mon, Feb 20, 2017 at 06:07:57PM -0800, Thomas Gleixner wrote: On Tue, 21 Feb 2017, Fengguang Wu wrote: Hi Marc, FYI here is another bisect result. The attached reproduce-* script can be used to reproduce the bug. Again. This is a problem in the calling code The WARN_ON merily shows

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

On Mon, Feb 20, 2017 at 06:07:57PM -0800, Thomas Gleixner wrote: On Tue, 21 Feb 2017, Fengguang Wu wrote: Hi Marc, FYI here is another bisect result. The attached reproduce-* script can be used to reproduce the bug. Again. This is a problem in the calling code The WARN_ON merily shows

email/patch test requests to 0day robot

On Mon, Feb 20, 2017 at 10:35:51AM +0100, Borislav Petkov wrote: On Mon, Feb 20, 2017 at 11:03:52AM +0800, Fengguang Wu wrote: We actually already test LKML patch in that way (Xiaolong maintains this feature). Nevertheless if developers specify "base-commit:" it could help

email/patch test requests to 0day robot

On Mon, Feb 20, 2017 at 10:35:51AM +0100, Borislav Petkov wrote: On Mon, Feb 20, 2017 at 11:03:52AM +0800, Fengguang Wu wrote: We actually already test LKML patch in that way (Xiaolong maintains this feature). Nevertheless if developers specify "base-commit:" it could help

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hi Borislav, On Sun, Feb 19, 2017 at 02:50:19PM +0100, Borislav Petkov wrote: On Sun, Feb 19, 2017 at 09:06:51AM +0800, Fengguang Wu wrote: Yes if we add it as a line below the branch URL, it could be a time saver. Right. Since it's hard to teach ALL people about the rule, it'd be best

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hi Borislav, On Sun, Feb 19, 2017 at 02:50:19PM +0100, Borislav Petkov wrote: On Sun, Feb 19, 2017 at 09:06:51AM +0800, Fengguang Wu wrote: Yes if we add it as a line below the branch URL, it could be a time saver. Right. Since it's hard to teach ALL people about the rule, it'd be best

Re: Crosstool/kbuild-all toolchain updates

Hi Stafford, On Wed, Feb 01, 2017 at 07:44:38AM +0900, Stafford Horne wrote: Hi Fengguang/All, I am working as the OpenRISC linux kernel maintainer. Currently in linux-next our patches are causing kbuild test robot to fail. This is because the patches are taking advantage of 2 'new' (2 year

Re: Crosstool/kbuild-all toolchain updates

Hi Stafford, On Wed, Feb 01, 2017 at 07:44:38AM +0900, Stafford Horne wrote: Hi Fengguang/All, I am working as the OpenRISC linux kernel maintainer. Currently in linux-next our patches are causing kbuild test robot to fail. This is because the patches are taking advantage of 2 'new' (2 year

Re: [PATCH] make.cross: Update openrisc toolchain to fix builds

Applied, thank you! On Sun, Feb 19, 2017 at 05:14:36PM +0900, Stafford Horne wrote: The latest openrisc kernel patchs in linux-next are failing to build due to old toolchains at the crosstool website. Update to point the the toolchain binaries released the OpenRISC team. Signed-off-by:

Re: [PATCH] make.cross: Update openrisc toolchain to fix builds

Applied, thank you! On Sun, Feb 19, 2017 at 05:14:36PM +0900, Stafford Horne wrote: The latest openrisc kernel patchs in linux-next are failing to build due to old toolchains at the crosstool website. Update to point the the toolchain binaries released the OpenRISC team. Signed-off-by:

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

On Sun, Feb 19, 2017 at 01:10:47AM +0100, Borislav Petkov wrote: Hey Fengguang, On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote: Good point! I noticed it too while sending out the report. It'll be showed as this in future: https://github.com/0day-ci/linux/commits/Borislav

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

On Sun, Feb 19, 2017 at 01:10:47AM +0100, Borislav Petkov wrote: Hey Fengguang, On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote: Good point! I noticed it too while sending out the report. It'll be showed as this in future: https://github.com/0day-ci/linux/commits/Borislav

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hi Borislav, On Sat, Feb 18, 2017 at 03:48:00PM +0100, Borislav Petkov wrote: Guys, please fix the 0day bot reporting. See below for more info. On Sat, Feb 18, 2017 at 01:01:53PM +0800, Fengguang Wu wrote: Greetings, 0day kernel testing robot got the below dmesg and the first bad commit

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hi Borislav, On Sat, Feb 18, 2017 at 03:48:00PM +0100, Borislav Petkov wrote: Guys, please fix the 0day bot reporting. See below for more info. On Sat, Feb 18, 2017 at 01:01:53PM +0800, Fengguang Wu wrote: Greetings, 0day kernel testing robot got the below dmesg and the first bad commit

Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Andy, On Fri, Feb 17, 2017 at 10:12:36PM -0800, Andy Lutomirski wrote: On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu <fengguang...@intel.com> wrote: Greetings, FYI here is an old bug, however is still active in mainline kernel. https://git.kernel.org/pub/scm/linux/kernel/git/to

Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Andy, On Fri, Feb 17, 2017 at 10:12:36PM -0800, Andy Lutomirski wrote: On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote: Greetings, FYI here is an old bug, however is still active in mainline kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

[x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Greetings, FYI here is an old bug, however is still active in mainline kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit a75a3f6fc92888e4119744d8594ffdf748c3d444 Merge: d2bea73 3bd2951 Author: Linus Torvalds AuthorDate:

[x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Greetings, FYI here is an old bug, however is still active in mainline kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit a75a3f6fc92888e4119744d8594ffdf748c3d444 Merge: d2bea73 3bd2951 Author: Linus Torvalds AuthorDate: Tue Nov 3 18:59:10 2015 -0800

[x86/vsyscall] 3dc33bd30f Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Kees, It's an old patch, however the panic still happens in linux-next 20170217. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b Author: Kees Cook AuthorDate: Wed Aug 12 17:55:19 2015 -0700

[x86/vsyscall] 3dc33bd30f Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Kees, It's an old patch, however the panic still happens in linux-next 20170217. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b Author: Kees Cook AuthorDate: Wed Aug 12 17:55:19 2015 -0700 Commit: Ingo Molnar

[drm] bea5b158ff BUG: unable to handle kernel NULL pointer dereference at 0000000000000748

Greetings, FYI, this debug patch triggers BUG in DRM subsystem. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg

[drm] bea5b158ff BUG: unable to handle kernel NULL pointer dereference at 0000000000000748

Greetings, FYI, this debug patch triggers BUG in DRM subsystem. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg Kroah-Hartman

[x86/mm] e1a58320a3 WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page()

Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit e1a58320a38dfa72be48a0f1a3a92273663ba6db Author: Stephen Smalley AuthorDate: Mon Oct 5 12:55:20 2015

[x86/mm] e1a58320a3 WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page()

Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit e1a58320a38dfa72be48a0f1a3a92273663ba6db Author: Stephen Smalley AuthorDate: Mon Oct 5 12:55:20 2015 -0400 Commit: Ingo

[driver core] bea5b158ff WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6482 ata_port_detach

Hi Rob, We see this WARNING in both mainline and linux-next kernels. commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg Kroah-Hartman CommitDate: Wed Aug 31 15:13:55

[driver core] bea5b158ff WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6482 ata_port_detach

Hi Rob, We see this WARNING in both mainline and linux-next kernels. commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg Kroah-Hartman CommitDate: Wed Aug 31 15:13:55 2016 +0200 driver core: add test of

Re: [kbuild-all] drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init'

Hi Kalle, On Thu, Feb 16, 2017 at 03:18:48PM +0200, Kalle Valo wrote: Arend Van Spriel writes: On 16-2-2017 11:01, Kalle Valo wrote: Arend Van Spriel writes: On 16-2-2017 10:39, Rafał Miłecki wrote: On 02/16/2017 10:31 AM,

Re: [kbuild-all] drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init'

Hi Kalle, On Thu, Feb 16, 2017 at 03:18:48PM +0200, Kalle Valo wrote: Arend Van Spriel writes: On 16-2-2017 11:01, Kalle Valo wrote: Arend Van Spriel writes: On 16-2-2017 10:39, Rafał Miłecki wrote: On 02/16/2017 10:31 AM, Kalle Valo wrote: (Adding linux-wireless) Arend or Rafał,

Re: [kbuild-all] drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init'

Hi all, Yes sorry, it's a false report related to how we do bisects. CONFIG_BRCM_TRACING=y CONFIG_BRCMDBG=y but DEBUG is not defined. I think it would help if CONFIG_BRCMDBG set DEBUG or if some of the tests for DEBUG used CONFIG_BRCMDBG instead. Arend or Rafał, would you be able to look

Re: [kbuild-all] drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.c:58:6: error: redefinition of 'brcmf_debugfs_init'

Hi all, Yes sorry, it's a false report related to how we do bisects. CONFIG_BRCM_TRACING=y CONFIG_BRCMDBG=y but DEBUG is not defined. I think it would help if CONFIG_BRCMDBG set DEBUG or if some of the tests for DEBUG used CONFIG_BRCMDBG instead. Arend or Rafał, would you be able to look

Re: [of/unittest] 815d74b35e: BUG: unable to handle kernel NULL pointer dereference at 00000012

On Tue, Jan 31, 2017 at 11:41:09AM +0100, Peter Zijlstra wrote: On Mon, Jan 30, 2017 at 01:42:11PM -0500, Steven Rostedt wrote: I think you wanted to Cc Peter Zijlstra on this. He's the kernel maintainer for perf. I do the more generic tracing. > > [ 18.811069] CPU: 0 PID: 12140 Comm:

Re: [of/unittest] 815d74b35e: BUG: unable to handle kernel NULL pointer dereference at 00000012

On Tue, Jan 31, 2017 at 11:41:09AM +0100, Peter Zijlstra wrote: On Mon, Jan 30, 2017 at 01:42:11PM -0500, Steven Rostedt wrote: I think you wanted to Cc Peter Zijlstra on this. He's the kernel maintainer for perf. I do the more generic tracing. > > [ 18.811069] CPU: 0 PID: 12140 Comm:

Re: lkp: make.cross: old aarch64-gcc has been removed

On Thu, Jan 12, 2017 at 12:00:07PM +, Will Deacon wrote: Hi Fengguang, Masami, On Thu, Jan 12, 2017 at 11:31:57AM +0800, Fengguang Wu wrote: On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote: >BTW, I found that the old toolchain is archived in release.linaro.org. >So

Re: lkp: make.cross: old aarch64-gcc has been removed

On Thu, Jan 12, 2017 at 12:00:07PM +, Will Deacon wrote: Hi Fengguang, Masami, On Thu, Jan 12, 2017 at 11:31:57AM +0800, Fengguang Wu wrote: On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote: >BTW, I found that the old toolchain is archived in release.linaro.org. >So

Re: lkp: make.cross: old aarch64-gcc has been removed

BTW, I found that the old toolchain is archived in release.linaro.org. So I made a patch for that. Applied the patch, thank you! Regards, Fengguang

Re: lkp: make.cross: old aarch64-gcc has been removed

BTW, I found that the old toolchain is archived in release.linaro.org. So I made a patch for that. Applied the patch, thank you! Regards, Fengguang

Re: lkp: make.cross: old aarch64-gcc has been removed

Hi Masami, On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote: Ping? Oops, sorry for overlooking your previous email! BTW, I found that the old toolchain is archived in release.linaro.org. So I made a patch for that. So there are gcc 4.9, 5, 6 versions available for aarch64.

Re: lkp: make.cross: old aarch64-gcc has been removed

Hi Masami, On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote: Ping? Oops, sorry for overlooking your previous email! BTW, I found that the old toolchain is archived in release.linaro.org. So I made a patch for that. So there are gcc 4.9, 5, 6 versions available for aarch64.

[usb_add_gadget_udc_release] bea5b158ff WARNING: CPU: 0 PID: 1 at lib/kobject.c:597 kobject_get

Greetings, Here is an USB WARNING triggered by Rob's test patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg

[usb_add_gadget_udc_release] bea5b158ff WARNING: CPU: 0 PID: 1 at lib/kobject.c:597 kobject_get

Greetings, Here is an USB WARNING triggered by Rob's test patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg Kroah-Hartman

[ata] bea5b158ff WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6482 ata_port_detach

Greetings, Here is an libata WARNING triggered by Rob's test patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg

[ata] bea5b158ff WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6482 ata_port_detach

Greetings, Here is an libata WARNING triggered by Rob's test patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg Kroah-Hartman

[drm] bea5b158ff WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/drm_crtc.c:5776 drm_mode_config_cleanup

Greetings, Here is another DRM WARNING triggered by Rob's test patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg

[drm] bea5b158ff WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/drm_crtc.c:5776 drm_mode_config_cleanup

Greetings, Here is another DRM WARNING triggered by Rob's test patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b158ff0da9c7246ff391f754f5f38e34577a Author: Rob Herring AuthorDate: Thu Aug 11 10:20:58 2016 -0500 Commit: Greg Kroah-Hartman

Re: [kbuild-all] 答复： Re: [PATCH 1/2] ocfs2: add kobject for online file check

Hi Gang, On Mon, Dec 19, 2016 at 06:43:48PM -0700, Gang He wrote: Hello Kbuild, Could you build my whole patch set (2 patch)? I think that the code is OK. We test your whole patch as well as first-N patches, and noticed that the first-1 patch breaks bisectibility: Note: the

Re: [kbuild-all] 答复： Re: [PATCH 1/2] ocfs2: add kobject for online file check

Hi Gang, On Mon, Dec 19, 2016 at 06:43:48PM -0700, Gang He wrote: Hello Kbuild, Could you build my whole patch set (2 patch)? I think that the code is OK. We test your whole patch as well as first-N patches, and noticed that the first-1 patch breaks bisectibility: Note: the

Re: [kbuild-all] arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'

On Tue, Dec 13, 2016 at 05:02:40AM +0100, Ralf Baechle wrote: On Sun, Dec 11, 2016 at 09:04:48AM +0800, kbuild test robot wrote: FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head:

Re: [kbuild-all] arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'

On Tue, Dec 13, 2016 at 05:02:40AM +0100, Ralf Baechle wrote: On Sun, Dec 11, 2016 at 09:04:48AM +0800, kbuild test robot wrote: FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head:

Re: [LKP] [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c

Hi Paul, Attached is the new dmesg. On Wed, Nov 30, 2016 at 05:39:50AM +0800, Ye Xiaolong wrote: On 11/29, Paul E. McKenney wrote: On Tue, Nov 29, 2016 at 05:21:19PM +, Sudeep Holla wrote: On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot wrote: > > FYI, we

Re: [LKP] [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c

Hi Paul, Attached is the new dmesg. On Wed, Nov 30, 2016 at 05:39:50AM +0800, Ye Xiaolong wrote: On 11/29, Paul E. McKenney wrote: On Tue, Nov 29, 2016 at 05:21:19PM +, Sudeep Holla wrote: On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot wrote: > > FYI, we noticed the following

Re: [kbuild-all] drivers/staging/greybus/bootrom.c:298:35-39: ERROR: fw is NULL but dereferenced.

On Mon, Nov 28, 2016 at 09:59:52AM +0100, Julia Lawall wrote: On Mon, 28 Nov 2016, Fengguang Wu wrote: On Sun, Nov 27, 2016 at 12:06:33PM +0100, Greg KH wrote: > On Sun, Nov 27, 2016 at 07:11:46AM +0800, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/k

Re: [kbuild-all] drivers/staging/greybus/bootrom.c:298:35-39: ERROR: fw is NULL but dereferenced.

On Mon, Nov 28, 2016 at 09:59:52AM +0100, Julia Lawall wrote: On Mon, 28 Nov 2016, Fengguang Wu wrote: On Sun, Nov 27, 2016 at 12:06:33PM +0100, Greg KH wrote: > On Sun, Nov 27, 2016 at 07:11:46AM +0800, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/k

Re: drivers/staging/greybus/bootrom.c:298:35-39: ERROR: fw is NULL but dereferenced.

On Sun, Nov 27, 2016 at 12:06:33PM +0100, Greg KH wrote: On Sun, Nov 27, 2016 at 07:11:46AM +0800, kbuild test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a0d60e62ea5c88a9823410e9d0929a513e29dea2 commit:

Re: drivers/staging/greybus/bootrom.c:298:35-39: ERROR: fw is NULL but dereferenced.

On Sun, Nov 27, 2016 at 12:06:33PM +0100, Greg KH wrote: On Sun, Nov 27, 2016 at 07:11:46AM +0800, kbuild test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a0d60e62ea5c88a9823410e9d0929a513e29dea2 commit:

Re: [LKP] [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

On Tue, Nov 22, 2016 at 11:07:16PM -0800, Linus Torvalds wrote: On Tue, Nov 22, 2016 at 10:44 PM, Fengguang Wu <fengguang...@intel.com> wrote: On Tue, Nov 22, 2016 at 02:04:42PM -0800, Linus Torvalds wrote: I also noticed that the kernel test robot had screwed up the participant

Re: [LKP] [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

On Tue, Nov 22, 2016 at 11:07:16PM -0800, Linus Torvalds wrote: On Tue, Nov 22, 2016 at 10:44 PM, Fengguang Wu wrote: On Tue, Nov 22, 2016 at 02:04:42PM -0800, Linus Torvalds wrote: I also noticed that the kernel test robot had screwed up the participants list for some reason, and had

Re: [LKP] [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

Hi Linus, On Tue, Nov 22, 2016 at 02:04:42PM -0800, Linus Torvalds wrote: [snip] I also noticed that the kernel test robot had screwed up the participants list for some reason, and had "Acked-by: Alexander Duyck , David S. Miller" as one of

Re: [LKP] [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

Hi Linus, On Tue, Nov 22, 2016 at 02:04:42PM -0800, Linus Torvalds wrote: [snip] I also noticed that the kernel test robot had screwed up the participants list for some reason, and had "Acked-by: Alexander Duyck , David S. Miller" as one of the participants. So there's some odd commit

Re: [PATCH] HID: lg: fix noderef.cocci warnings

On Tue, Nov 22, 2016 at 11:44:34AM +0100, Jiri Kosina wrote: On Mon, 21 Nov 2016, Benjamin Tissoires wrote: > Generated by: scripts/coccinelle/misc/noderef.cocci > > CC: Benjamin Tissoires <benjamin.tissoi...@redhat.com> > Signed-off-by: Fengguang Wu <fengguang...@inte

Re: [PATCH] HID: lg: fix noderef.cocci warnings

On Tue, Nov 22, 2016 at 11:44:34AM +0100, Jiri Kosina wrote: On Mon, 21 Nov 2016, Benjamin Tissoires wrote: > Generated by: scripts/coccinelle/misc/noderef.cocci > > CC: Benjamin Tissoires > Signed-off-by: Fengguang Wu > --- > > hid-lg.c |6 -- > 1 file cha

Re: [kbuild-all] [Patch v6.1] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

Hi He Chen, On Tue, Nov 15, 2016 at 02:02:23PM +0800, He Chen wrote: On Tue, Nov 15, 2016 at 04:24:39AM +0800, kbuild test robot wrote: Hi He, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.9-rc5] [cannot apply to next-20161114] [if your patch is applied to the wrong

Re: [kbuild-all] [Patch v6.1] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

Hi He Chen, On Tue, Nov 15, 2016 at 02:02:23PM +0800, He Chen wrote: On Tue, Nov 15, 2016 at 04:24:39AM +0800, kbuild test robot wrote: Hi He, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.9-rc5] [cannot apply to next-20161114] [if your patch is applied to the wrong

Re: [PATCH v4] KVM: x86: emulate FXSAVE and FXRSTOR

CC Xiaolong. On Wed, Nov 09, 2016 at 07:46:28PM +0100, Radim Krčmář wrote: 2016-11-10 02:42+0800, kbuild test robot: Hi Radim, And I even replied to the series, so this would happen ... Btw. would the tool recognize it if the header was [PATCH v4 4/4]? [auto build test ERROR on

Re: [PATCH v4] KVM: x86: emulate FXSAVE and FXRSTOR

CC Xiaolong. On Wed, Nov 09, 2016 at 07:46:28PM +0100, Radim Krčmář wrote: 2016-11-10 02:42+0800, kbuild test robot: Hi Radim, And I even replied to the series, so this would happen ... Btw. would the tool recognize it if the header was [PATCH v4 4/4]? [auto build test ERROR on

Re: scripts/gcc-plugins/gcc-common.h:4:22: fatal error: bversion.h: No such file or directory

Hi Emese, On Sun, Nov 06, 2016 at 09:19:05AM +0100, Emese Revfy wrote: On Sun, 6 Nov 2016 07:09:57 +0800 kbuild test robot wrote: Hi Emese, FYI, the error/warning still remains. ++(scripts/gcc-plugin.sh:12): main(): gcc-4.6 -E -x c++ - -o /dev/null

Re: scripts/gcc-plugins/gcc-common.h:4:22: fatal error: bversion.h: No such file or directory

Hi Emese, On Sun, Nov 06, 2016 at 09:19:05AM +0100, Emese Revfy wrote: On Sun, 6 Nov 2016 07:09:57 +0800 kbuild test robot wrote: Hi Emese, FYI, the error/warning still remains. ++(scripts/gcc-plugin.sh:12): main(): gcc-4.6 -E -x c++ - -o /dev/null -Iscripts/gcc-plugins

Re: [PATCH RFC 0/4] Fix PDF build errors

On Wed, Nov 02, 2016 at 03:27:50PM +0200, Jani Nikula wrote: On Wed, 02 Nov 2016, Mauro Carvalho Chehab wrote: Em Wed, 02 Nov 2016 13:14:47 +0200 Jani Nikula escreveu: On Wed, 02 Nov 2016, Mauro Carvalho Chehab

Re: [PATCH RFC 0/4] Fix PDF build errors

On Wed, Nov 02, 2016 at 03:27:50PM +0200, Jani Nikula wrote: On Wed, 02 Nov 2016, Mauro Carvalho Chehab wrote: Em Wed, 02 Nov 2016 13:14:47 +0200 Jani Nikula escreveu: On Wed, 02 Nov 2016, Mauro Carvalho Chehab wrote: > This series address a series of errors during PDF generation from >

Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f

On Mon, Oct 31, 2016 at 12:58:14PM +0800, Fengguang Wu wrote: Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot <fengguang...@intel.com> wrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin

Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f

On Mon, Oct 31, 2016 at 12:58:14PM +0800, Fengguang Wu wrote: Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot wrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

Re: [LKP] [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression

Hi Thomas, It's been a big challenge that we'll occasionally run into such bisect whose data show clear changes, however cannot be easily explained by looking at the code logic. On Fri, Oct 28, 2016 at 12:37:45AM +0200, Thomas Gleixner wrote: On Thu, 27 Oct 2016, Ye Xiaolong wrote: Yes, this

Re: [LKP] [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression

Hi Thomas, It's been a big challenge that we'll occasionally run into such bisect whose data show clear changes, however cannot be easily explained by looking at the code logic. On Fri, Oct 28, 2016 at 12:37:45AM +0200, Thomas Gleixner wrote: On Thu, 27 Oct 2016, Ye Xiaolong wrote: Yes, this

Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f

Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot wrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge

Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f

Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot wrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge

Re: drivers/base/power/opp/of.c:181:6: error: redefinition of 'dev_pm_opp_of_remove_table'

On Fri, Oct 28, 2016 at 09:27:53AM +0530, Viresh Kumar wrote: On 28-10-16, 07:22, kbuild test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: e3300ffef0653774f1099cab153d25d24bd773ce commit: f47b72a15a9679dd4dc1af681d4d2f1ca2815552 PM /

Re: drivers/base/power/opp/of.c:181:6: error: redefinition of 'dev_pm_opp_of_remove_table'

On Fri, Oct 28, 2016 at 09:27:53AM +0530, Viresh Kumar wrote: On 28-10-16, 07:22, kbuild test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: e3300ffef0653774f1099cab153d25d24bd773ce commit: f47b72a15a9679dd4dc1af681d4d2f1ca2815552 PM /

<    1   2   3   4   5   6   7   8   9   10   >