Re: [LKP] [patch v2 for-4.20] mm, thp: restore node-local hugepage allocations

2018-12-05 Thread kernel test robot
On Wed, Dec 05, 2018 at 02:46:50PM -0800, David Rientjes wrote: > This is a full revert of ac5b2c18911f ("mm: thp: relax __GFP_THISNODE for > MADV_HUGEPAGE mappings") and a partial revert of 89c83fb539f9 ("mm, thp: > consolidate THP gfp handling into alloc_hugepage_direct_gfpmask"). > > By not

[locking/lockdep] f069edd342: WARNING:at_kernel/locking/lockdep.c:#register_lock_class

2018-12-04 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: f069edd34280c56ed36bf35cc255c719df430abd ("locking/lockdep: Free lock classes that are no longer in use") https://github.com/bvanassche/linux for-next in testcase: trinity with following parameters: runtime: 300s

[NFS] b4e004cd5d: BUG:KASAN:null-ptr-deref_in_s

2018-12-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: b4e004cd5da022650322c64e5c829443e55cb7e2 ("NFS: Add fs_context support.") https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git Q19 in testcase: trinity with following parameters: runtime: 300s test-description:

[locking/lockdep] fe7e1ef5c1: WARNING:at_kernel/locking/lockdep.c:#register_lock_class

2018-11-29 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: fe7e1ef5c1044f3ef122b877b078a47e74360dea ("locking/lockdep: Complain if a lock object has no name") https://github.com/bvanassche/linux for-next in testcase: trinity with following parameters: runtime: 300s

[locking/lockdep] 62f18467c4: WARNING:at_kernel/locking/lockdep.c:#register_lock_class

2018-11-29 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 62f18467c40065cae25a8e52c41de0d9771cfd24 ("locking/lockdep: Complain if a lock object has no name") https://github.com/bvanassche/linux for-next in testcase: trinity with following parameters: runtime: 300s

Re: [PATCH] locks: fix performance regressions.

2018-11-28 Thread kernel test robot
Hi, On Wed, Nov 28, 2018 at 11:53:48AM +1100, NeilBrown wrote: > > The kernel test robot reported two performance regressions > caused by recent patches. > Both appear to related to the global spinlock blocked_lock_lock > being taken more often. > > This patch av

[LKP] [mm] fb420465c9: kernel_BUG_at_mm/slub.c

2018-11-22 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: fb420465c9bcaf57aa6bff76ffe31add559ae1f9 ("[PATCH] mm: use this_cpu_cmpxchg_double in put_cpu_partial") url: https://github.com/0day-ci/linux/commits/Wengang-Wang/mm-use-this_cpu_cmpxchg_double-in-put_cpu_partial/20181119-215159

[LKP] [xarray] 0e9446c35a: WARNING:at_include/linux/xarray.h:#xa_mk_value

2018-11-04 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 0e9446c35a80931044b6d8d2d74a9cabd248539f ("xarray: Add range store functionality") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

[LKP] 499ac3b60f [ 2.479301] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:328 __debug_object_init

2018-10-29 Thread kernel test robot
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 499ac3b60f657dae82055fc81c7b01e6242ac9bc Author: Paul Blakey AuthorDate: Sun Mar 4 17:29:49 2018 +0200 Commit: David S.

[LKP] [mm] 68c37ccedc: BUG:kernel_hang_in_early-boot_stage,last_printk:early_console_in_setup_code

2018-10-29 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 68c37ccedcde10514898f4ba3b28c0de85c590d1 ("mm: nobootmem: remove bootmem allocation APIs") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm

[LKP] bd00db8b16 [ 48.718069] BUG: spinlock trylock failure on UP on CPU#0, kworker/u2:1/27

2018-10-18 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://github.com/bvanassche/linux for-next commit bd00db8b160b8cb2a61e6321aee5a68c6d823075 Author: Bart Van Assche AuthorDate: Tue Oct 16 13:57:06 2018 -0700 Commit: Bart Van Assche CommitDate: Wed

[LKP] ca90800a91 [ 9.462982] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:4061 __alloc_pages_nodemask

2018-10-12 Thread kernel test robot
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 ca90800a91ba723d78ded634d037c1d2df8b54d6 Author: Kees Cook AuthorDate: Thu May 10 16:40:03 2018 -0700 Commit: Kees Cook

[LKP] fde06e0775 [ 9.203072] kernel BUG at lib/list_debug.c:31!

2018-10-09 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit fde06e07750477f049f12d7d471ffa505338a3e7 Author: Pingfan Liu AuthorDate: Thu Oct 4 07:43:01 2018 +1000 Commit: Stephen

[LKP] [timens] 3cc8de9dcb: RIP:posix_get_boottime

2018-09-29 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 3cc8de9dcbe53955edcc65122f169666b4f6cbd9 ("[RFC 04/20] timens: Introduce CLOCK_BOOTTIME offset") url: https://github.com/0day-ci/linux/commits/Dmitry-Safonov/ns-Introduce-Time-Namespace/20180920-194322 in testcase: boot on test

[LKP] [rcutorture] 5aa56a54ce: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_fwd_prog

2018-09-29 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 5aa56a54ce92761e974f93592f69b75b8c2398a8 ("rcutorture: Add call_rcu() flooding forward-progress tests") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev in testcase: trinity with following parameters:

[LKP] [posix] 25217c6e39: BUG:KASAN:null-ptr-deref_in_c

2018-09-29 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 25217c6e39560eeadb338e0140ee215410200b67 ("[RFC 13/20] posix-timers/timens: Take into account clock offsets") url: https://github.com/0day-ci/linux/commits/Dmitry-Safonov/ns-Introduce-Time-Namespace/20180920-194322 in

[LKP] [mm, oom] 6209f6fc62: general_protection_fault:#[##]

2018-09-24 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 6209f6fc62835d84c2a92d237588a114e39436ce ("mm, oom: rework mmap_exit vs. oom_reaper synchronization") https://github.com/0day-ci/linux

[LKP] [x86/pci] 7ffb31888c: PANIC:early_exception

2018-09-18 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 7ffb31888cbaab36ec464fc43ecf5ddecdbd55ac ("[PATCH v7 07/16] x86/pci: Add Hygon Dhyana support to PCI and north bridge") url:

[LKP] [security] 8762c83c14: BUG:kernel_hang_in_test_stage

2018-09-18 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 8762c83c14e566226b11c68bf01ce7d5d70fee29 ("security: Kill off the sb_copy_data hook") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git btrfs-mount-api in testcase: trinity with following parameters:

[LKP] [vfree, kvfree] a79ed8bfb2: BUG:sleeping_function_called_from_invalid_context_at_mm/util.c

2018-09-18 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: a79ed8bfb24e899aa55de42703ae4508ff016311 ("[PATCH 3/3] vfree, kvfree: Add debug might sleeps.") url: https://github.com/0day-ci/linux/commits/Andrey-Ryabinin/kvfree-Fix-misleading-comment/20180915-094734 in testcase: trinity

[LKP] [x86/mm/cpa] 68ad427583: WARNING:at_arch/x86/mm/pageattr.c:#__change_page_attr

2018-09-18 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 68ad4275838d223a06a3211fb2f27c8b6f44cd24 ("x86/mm/cpa: Add sanity check for existing mappings") https://github.com/0day-ci/linux

[LKP] [x86/mm/cpa] c77d419f92: WARNING:at_arch/x86/mm/pageattr.c:#__change_page_attr_set_clr

2018-09-16 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: c77d419f9248f8c40bbf773d59aa5b6cbc0d60f0 ("[patch V2 07/10] x86/mm/cpa: Add sanity check for existing mappings") url:

[LKP] [ipc] 61224adcd2: general_protection_fault:#[##]

2018-09-12 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 61224adcd25b0abd01f02459e82b30735161e723 ("ipc: Convert mqueue fs to fs_context") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: trinity with following parameters: runtime: 300s

[LKP] [rcu] 02a5c550b2: BUG:kernel_reboot-without-warning_in_test_stage

2018-09-11 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 02a5c550b2738f2bfea8e1e00aa75944d71c9e18 ("rcu: Abstract extended quiescent state determination") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: perf_event_tests with following parameters:

[LKP] [kernel] 92114220fe: BUG:unable_to_handle_kernel

2018-09-11 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 92114220fe6a374172e99261b6451c515d29c8dc ("[PATCH] kernel: prevent submission of creds with higher privileges inside container") url:

[LKP] [kernfs, sysfs, cgroup, intel_rdt] a8c7fe83d1: BUG:kernel_hang_in_test_stage

2018-09-10 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: a8c7fe83d17109b77c7b27a23140e76d3753fa6a ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git btrfs-mount-api in testcase: trinity with following parameters:

[LKP] [vfs] fd0002870b: BUG:KASAN:null-ptr-deref_in_n

2018-09-10 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: fd0002870b453c58d0d8c195954f5049bc6675fb ("vfs: Implement a filesystem superblock creation/configuration context") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine:

[LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: Hold tty_ldisc_lock() during tty_reopen()") url: https://github.com/0day-ci/linux/commits/Dmitry-Safonov/tty-Hold-write-ldisc-sem-in-tty_reopen/20180829-165618 base:

[LKP] [rcutorture] 894b343aa8: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_fwd_prog

2018-09-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 894b343aa8bec5ee732329f1db09b9f5c2794de5 ("rcutorture: Add call_rcu() flooding forward-progress tests") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev.2018.08.30a in testcase: trinity with following

[lkp-robot] [x86] 19efe000d3: PANIC:double_fault

2018-08-22 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: 19efe000d3258032d9a1dfb25313a092f9454da0 ("x86: Remap the IRQ stack so it has guard pages") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/guard_pages in testcase: trinity with following parameters:

[LKP] [mm, oom] c1e4c54f9c: BUG:KASAN:null-ptr-deref_in_d

2018-07-30 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: c1e4c54f9c750fc3ea4715f5363b92ea4d4efb29 ("mm, oom: reorganize the oom report in dump_header") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64

[LKP] [rcutorture] 3b745c8969: WARNING:at_mm/slab_common.c:#kmalloc_slab

2018-07-26 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: 3b745c8969c752601cb68c82a06735363563ab42 ("rcutorture: Make boost test more robust") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -smp

[LKP] [ovl] 24c944dd64: BUG:kernel_reboot-without-warning_in_boot_stage

2018-07-25 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 24c944dd64f807542a2ec72744c81f064d1a60da ("ovl: Modify ovl_lookup() and friends to lookup metacopy dentry") https://git.kernel.org/cgit/linux/kernel/git/mszeredi/vfs.git overlayfs-next in testcase: boot on test machine:

[lkp-robot] [confidence: ] e181ae0c5d [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at 00000000

2018-07-20 Thread kernel test robot
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 e181ae0c5db9544de9c53239eb22bc012ce75033 Author: Pavel Tatashin AuthorDate: Sat Jul 14 09:15:07 2018 -0400 Commit:

[lkp-robot] [afs] 5b86d4ff5d: BUG:unable_to_handle_kernel

2018-07-16 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 5b86d4ff5dce3271dff54119e06174dc22422903 ("afs: Implement network namespacing") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [debugobjects] 3f96d20faf: WARNING:at_kernel/locking/lockdep.c:#register_lock_class

2018-07-15 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 3f96d20fafb19e6dd869362ace53662b06e6f6c1 ("[PATCH] debugobjects: Disable lockdep tracking of debugobjects internal locks") url:

[lkp-robot] [xarray] f0b90e702f: BUG:soft_lockup-CPU##stuck_for#s

2018-07-12 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: f0b90e702fe74fa575b7382ec3474d341098d5b1 ("xarray: Add XArray unconditional store operations") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-i386

[lkp-robot] [perf tests] 32a4debc7c: perf-sanity-tests.probe_libc's_inet_pton_&_backtrace_it_with_ping.fail

2018-07-04 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 32a4debc7c89ee5e29c0bbdfdd3ae0ce0e01057f ("[PATCH] perf tests: Fix regex for record+probe_libc_inet_pton.sh") url:

[lkp-robot] [rcu] e46874dd99: WARNING:suspicious_RCU_usage

2018-07-04 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: e46874dd99fa8ef78802bee8e80fe2844ae95cd1 ("[PATCH RFC tip/core/rcu 1/2] rcu: Defer reporting RCU-preempt quiescent states when disabled") url:

[lkp-robot] [rcu] 50b7ae6af5: BUG:spinlock_recursion_on_CPU

2018-07-03 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 50b7ae6af5671168cc6cf2de959b02584e4c3f87 ("rcu: Diagnostics for grace-period hangs") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] 9a93848fe7 [ 1.383411] WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:235 note_page

2018-07-02 Thread kernel test robot
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 9a93848fe787a53aec404e4e00d8f7f9bbdaebb4 Author: Peter Zijlstra AuthorDate: Thu Feb 2 14:43:51 2017 +0100 Commit: Ingo

[lkp-robot] ee410f15b1 BUG: kernel hang in boot stage

2018-07-02 Thread kernel test robot
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 ee410f15b1418f2f4428e79980674c979081bcb7 Author: Thierry Escande AuthorDate: Thu Jun 14 15:28:15 2018 -0700 Commit:

[lkp-robot] [x86/kernel] b1ff47aace: WARNING:at_kernel/jump_label.c:#__jump_label_update

2018-07-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: b1ff47aacea95e5be1bedf2aee740395b52f4591 ("[PATCH 5/5] x86/kernel: jump_table: use relative references") url:

[lkp-robot] [bisect done] ca90800a91 [ 1.761734] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:4061 __alloc_pages_nodemask

2018-06-25 Thread kernel test robot
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 ca90800a91ba723d78ded634d037c1d2df8b54d6 Author: Kees Cook AuthorDate: Thu May 10 16:40:03 2018 -0700 Commit: Kees Cook

[lkp-robot] [bisect done] 51bad67ffb [ 2.125035] int3: 0000 [#1] SMP DEBUG_PAGEALLOC

2018-06-25 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/debug commit 51bad67ffbce0aaa44579f84ef5d05597054ec6a Author: Alexey Dobriyan AuthorDate: Tue May 8 00:37:55 2018 +0300 Commit: Ingo

[lkp-robot] [bisect done] ef1433f717 [ 7.049860] BUG: unable to handle kernel NULL pointer dereference at 0000004c

2018-06-25 Thread kernel test robot
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 ef1433f717a2c63747a519d86965d73ff9bd08b3 Author: Kishon Vijay Abraham I AuthorDate: Mon Apr 2 18:59:35 2018 +0530 Commit:

[lkp-robot] [tty] b6da31b2c0: WARNING:possible_circular_locking_dependency_detected

2018-06-25 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: b6da31b2c07c46f2dcad1d86caa835227a16d9ff ("tty: Fix data race in tty_insert_flip_string_fixed_flag") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters:

[lkp-robot] [VFS] 56d9b2efe5: general_protection_fault:#[##]

2018-06-20 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 56d9b2efe552bceedd25e8efe0a0083ef9d541e6 ("VFS: Implement fsopen() to prepare for a mount") https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git mount-reordered in testcase: trinity with following parameters:

[lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-13 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 46e26223e39c64763e321f229e324be15179c505 ("rcutorture: Make boost test more robust") url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/rcutorture-Disable-RT-throttling-for-boost-tests/20180611-074731 base:

[lkp-robot] [x86/vdso] ab1bcc4420: BUG:kernel_hang_in_boot_stage

2018-06-13 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: ab1bcc442070315bd0ce963331d5bb93d5c5476e ("x86/vdso: Move out the CPU number store") url: https://github.com/0day-ci/linux/commits/Chang-S-Bae/x86-fsgsbase-64-Introduce-FS-GS-base-helper-functions/20180605-095329 in testcase:

[lkp-robot] [kernfs, sysfs, cgroup, intel_rdt] 0dd4eca846: kernel_BUG_at_fs/super.c

2018-06-13 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 0dd4eca846629b5dc7d11ca40ae2a1379334b9e4 ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: trinity with following parameters:

[lkp-robot] [watchdog/softlockup] 4808e7a5dc: BUG:KASAN:null-ptr-deref_in_h

2018-06-12 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: 4808e7a5dc055fd8776e6b59e02775730ea716f6 ("watchdog/softlockup: Replace "watchdog/%u" threads with cpu_stop_work") url: https://github.com/0day-ci/linux/commits/Peter-Zijlstra/kthread-smpboot-More-fixes/20180613-003329 in

[lkp-robot] [x86] 1a39381d70: WARNING:at_kernel/locking/mutex.c:#__mutex_unlock_slowpath

2018-06-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 1a39381d7f0097ec6e2ceb75812d6c00b2f1 ("x86: alternatives: macrofy locks for better inlining") url: https://github.com/0day-ci/linux/commits/Nadav-Amit/x86-macrofying-inline-asm-for-better-compilation/20180605-124313 in

[lkp-robot] [x86/vdso] f52001961d: BUG:kernel_hang_in_early-boot_stage,last_printk:Probing_EDD(edd=off_to_disable)...ok

2018-06-05 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: f52001961d6e5c397e40c4d440103288cdce9a79 ("x86/vdso: Move out the CPU number store") url: https://github.com/0day-ci/linux/commits/Chang-S-Bae/x86-Enable-FSGSBASE-instructions/20180602-125452 in testcase: boot on test machine:

[lkp-robot] [mm, oom] 2d251ff6e6: BUG:unable_to_handle_kernel

2018-06-03 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 2d251ff6e66d7978b3e7a9c69e99b7150de26926 ("mm, oom: fix unnecessary killing of additional processes") url:

[lkp-robot] [Print the memcg's name when system] c385a55f52: BUG:KASAN:null-ptr-deref_in_m

2018-05-30 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: c385a55f521e1649051d7f653bec9aa0ce711c9e ("Print the memcg's name when system-wide OOM happened") url: https://github.com/0day-ci/linux/commits/ufo19890607/Print-the-memcg-s-name-when-system-wide-OOM-happened/20180522-033834 in

[lkp-robot] [tty] b6da31b2c0: WARNING:possible_circular_locking_dependency_detected

2018-05-21 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: b6da31b2c07c46f2dcad1d86caa835227a16d9ff ("tty: Fix data race in tty_insert_flip_string_fixed_flag") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64

[lkp-robot] [workqueue] f303fccb82: kmsg.workqueue:round-robin_CPU_selection_forced,expect_performance_impact

2018-05-19 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: f303fccb82928790ec58eea82722bd5c54d300b3 ("workqueue: implement "workqueue.debug_force_rr_cpu" debug feature") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on test machine:

[lkp-robot] [x86/asm] 51bad67ffb: int3:#[##]

2018-05-15 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 51bad67ffbce0aaa44579f84ef5d05597054ec6a ("x86/asm: Pad assembly functions with INT3 instructions") https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/pti in testcase: boot on test machine: qemu-system-i386

[lkp-robot] [EXP rcu] 21560e1007: WARNING:possible_recursive_locking_detected

2018-05-07 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 21560e10077bf9f7baf69aa82527850271173862 ("EXP rcu: Diagnostics for grace-period hangs") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev.2018.05.01a in testcase: ebizzy with following parameters:

[lkp-robot] [rcu] 6ec8474821: WARNING:at_kernel/softirq.c:#__local_bh_enable_ip

2018-05-07 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 6ec84748215d9b0c91dba0b8674540e493ce2dcf ("rcu: Make simple callback acceleration refer to rdp->gp_seq_needed") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev.2018.05.01a in testcase: boot on test

[lkp-robot] [EXP rcu] aa09766fd9: BUG:spinlock_trylock_failure_on_UP_on_CPU

2018-05-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: aa09766fd96b09ef68c4cc0e09869d16c1c11182 ("EXP rcu: Diagnostics for grace-period hangs") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev.2018.04.27a in testcase: boot on test machine: qemu-system-x86_64

[lkp-robot] [kthread/smpboot] cad8e99675: inconsistent{IN-HARDIRQ-W}->{HARDIRQ-ON-W}usage

2018-04-28 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: cad8e9967526d263d9a4f04ca763b2d76c045750 ("kthread/smpboot: Serialize kthread parking against wakeup") url:

c9e97a1997 ("mm: initialize pages on demand during boot"): BUG: kernel reboot-without-warning in early-boot stage, last printk: early console in setup code

2018-04-24 Thread kernel test robot
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 c9e97a1997fbf3a1d18d4065c2ca381f0704d7e5 Author: Pavel Tatashin AuthorDate: Thu Apr 5 16:22:31

[lkp-robot] [kernfs, sysfs, cgroup, intel_rdt] f82b0d1249: kernel_BUG_at_fs/super.c

2018-04-22 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: f82b0d1249c32dec1ae94fd8caf478627c4752b7 ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: boot on test machine:

[lkp-robot] [hugetlbfs] e979e5a059: BUG_hugetlbfs_inode_cache(Not_tainted):Objects_remaining_in_hugetlbfs_inode_cache_on__kmem_cache_shutdown()

2018-04-09 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: e979e5a0591e70ad0b41cf876ee987de468a220e ("hugetlbfs: Convert to fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm

[lkp-robot] [hugetlbfs] bfa5d8e197: WARNING:possible_recursive_locking_detected

2018-04-09 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: bfa5d8e19798e76de39473b7ecf14f0ce08e8f78 ("hugetlbfs: Convert to fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: boot on test machine: qemu-system-i386 -enable-kvm -cpu

[lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

2018-04-08 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have printk come through the trace events for initcall_debug") url: https://github.com/0day-ci/linux/commits/Steven-Rostedt/init-tracing/20180407-130743 in testcase:

[lkp-robot] [list_lru] 42658d54ce: BUG:unable_to_handle_kernel

2018-04-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 42658d54ce4d9c25c8a286651c60cbc869f2f91e ("list_lru: Add memcg argument to list_lru_from_kmem()") url:

[staging] 184ecc5ceb: BUG:unable_to_handle_kernel

2018-03-19 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 184ecc5ceb379b43b29fc373f497fca88c73ad38 ("staging: lustre: allow monolithic builds") https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git staging-testing in testcase: trinity with following parameters:

[ACPI / processor] c1294b481b: WARNING:at_include/linux/cpumask.h:#invoke_rcu_core

2018-03-19 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: c1294b481baa89caa30b4c2933c5ce662d52070c ("ACPI / processor: Fix possible CPUs map") url: https://github.com/0day-ci/linux/commits/Dou-Liyang/ACPI-processor-Fix-possible-CPUs-map/20180318-023857 in testcase: boot on test

[tracing] 45382b2a36: WARNING:at_kernel/locking/lockdep.c:#check_flags

2018-03-17 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 45382b2a369a50f62c64e07cb6f59992baeb9479 ("tracing: Improve design of preemptirq tracepoints and its users") url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/Improve-preemptirq-tracepoint-usage/20180317-155535 in

[ACPI / processor] d619c81e24: WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu

2018-03-16 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: d619c81e246424e322f7a902bed6e60b90668d56 ("ACPI / processor: Get accurate possible CPU count") url: https://github.com/0day-ci/linux/commits/Dou-Liyang/ACPI-processor-Get-accurate-possible-CPU-count/20180316-140349 in testcase:

[ACPI / processor] d619c81e24: WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu

2018-03-16 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: d619c81e246424e322f7a902bed6e60b90668d56 ("ACPI / processor: Get accurate possible CPU count") url: https://github.com/0day-ci/linux/commits/Dou-Liyang/ACPI-processor-Get-accurate-possible-CPU-count/20180316-140349 in testcase:

[tracing] b648360016: WARNING:at_kernel/locking/lockdep.c:#check_flags

2018-03-16 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: b648360016fd691bcb1128a6b7fa2473b3a53ed3 ("tracing: Improve design of preemptirq tracepoints and its users") url:

94d3a25408: kernel_BUG_at_kernel/fork.c

2018-03-09 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 94d3a254089a7cd4f11b7071b4323afd98eea0a6 ("Detect early free of a live mm") url: https://github.com/0day-ci/linux/commits/Mark-Rutland/Detect-early-free-of-a-live-mm/20180303-144149 in testcase: boot on test machine:

[lkp-robot] [hugetlbfs] 49977c3afc: BUG_hugetlbfs_inode_cache(Not_tainted):Objects_remaining_in_hugetlbfs_inode_cache_on__kmem_cache_shutdown()

2018-03-08 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 49977c3afcdd2d94237d4bf6866d3515c60762be ("hugetlbfs: Convert to fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: trinity with following parameters: runtime: 300s

[kernfs, sysfs, cgroup, intel_rdt] 6393e11b84: kernel_BUG_at_fs/super.c

2018-03-08 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-6): commit: 6393e11b84a5116ea99d7a05d0dcada2acea347f ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: trinity with following parameters:

[EXP softirq] 3f6b5ffc70: Kernel_panic-not_syncing:kmem_cache_create:Failed_to_create_slab'pid'.Error

2018-03-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 3f6b5ffc706a54598b82456ae0be395aa6465982 ("EXP softirq: Is it possible to RCUify BH disable/enable?") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev.2018.03.01a in testcase: boot on test machine:

[lkp-robot] [bisect done] e1a58320a3 [ 1.083188] WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page()

2018-03-04 Thread kernel test robot
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

[of] b013aa45d2: kernel_BUG_at_arch/x86/mm/physaddr.c

2018-03-02 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-5): commit: b013aa45d2168019984aec70e00d09cf0a4a00c5 ("of: add early boot allocation of of_find_node_by_phandle() cache") url:

[lkp-robot] [mm] df2af627c7: BUG:sleeping_function_called_from_invalid_context_at_include/linux/percpu-rwsem.h

2018-02-27 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: df2af627c79ad4273b4b4c49711252c084490fd2 ("mm: initialize pages on demand during boot") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m

91f606a8fa ("x86/mm: Replace compile-time checks for 5-level .."): BUG: kernel reboot-without-warning in boot stage

2018-02-26 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm commit 91f606a8fa68264224cbc76888fa8649cdbe9990 Author: Kirill A. Shutemov AuthorDate: Wed Feb 14

[rcu] df95cc69cc: BUG:KASAN:null-ptr-deref_in__lock_acquire

2018-02-23 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: df95cc69cca894430640237d39453f5d96c40a7d ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

[lkp-robot] [rcu] 056becf54e: BUG:KASAN:null-ptr-deref_in__lock_acquire

2018-02-23 Thread kernel test robot
TO: Paul E. McKenney CC: LKML , Paul E. McKenney , linux-kernel@vger.kernel.org, l...@01.org FYI, we noticed the following commit (built with gcc-7): commit: 056becf54ef1ab39db14a66625353899dba6762f ("rcu:

[lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c

2018-02-23 Thread kernel test robot
TO: Petr Mladek CC: Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Linus

[rcu] 858c7b0986: BUG:KASAN:null-ptr-deref_in__lock_acquire

2018-02-23 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 858c7b0986b397d4960612f03a0ef00be69a8d3f ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

[rcu] 11d88c8120: general_protection_fault:#[##]

2018-02-22 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 11d88c812043b17c016b8dbe931244f74f082281 ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: boot on test machine: qemu-system-x86_64

[of] 965aa3fac0: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h

2018-02-13 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 965aa3fac087bd026f614824b821ef0238e77d60 ("of: cache phandle nodes to decrease cost of of_find_node_by_phandle()") url:

[tracing] 8e130b0d92: WARNING:at_kernel/rcu/tree.c:#rcu_irq_exit

2018-02-07 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 8e130b0d9284a0a01ca1d6ecf8f0896cfc28b112 ("tracing: Improve design of preemptirq tracepoints and its users") url:

[tracing] 8e130b0d92: WARNING:at_kernel/rcu/tree.c:#rcu_irq_exit

2018-02-07 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 8e130b0d9284a0a01ca1d6ecf8f0896cfc28b112 ("tracing: Improve design of preemptirq tracepoints and its users") url:

[lkp-robot] [rcu] 5bb856a179: WARNING:at_kernel/workqueue.c:#flush_work

2018-02-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 5bb856a17977672f2142d06e68ac60e746e7bca2 ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

[lkp-robot] [mm] f7f99100d8: BUG:unable_to_handle_kernel

2018-02-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: f7f99100d8d95dbcf09e0216a143211e79418b9f ("mm: stop zeroing memory during allocation in vmemmap") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters:

[lkp-robot] [rcu] 6c0a1d639c: BUG:scheduling_while_atomic

2018-02-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 6c0a1d639cb7e989007cc3153b2f4eafb2e5bb7b ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

[fw_cfg] c8bf448ff3: kernel_BUG_at_arch/x86/mm/physaddr.c

2018-02-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: c8bf448ff3899860de51fbae61a43619c912ddf2 ("fw_cfg: do DMA read operation") https://git.kernel.org/cgit/linux/kernel/git/mst/vhost.git vhost in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M caused below

[lkp-robot] [x86/kasan] def0e7b54d: Kernel_panic-not_syncing:memblock_virt_alloc_try_nid:Failed_to_allocate#bytes_align=#nid=#from=#max_addr=

2018-01-27 Thread kernel test robot
Hi, Andrey Is this panic log expected with your commit? FYI, we noticed the following commit (built with gcc-7): commit: def0e7b54d63bae120302a4957c272107563ad04 ("x86/kasan: Panic if there is not enough memory to boot") https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/pti in

[lkp-robot] [hugetlbfs] c0033af7ee: BUG_hugetlbfs_inode_cache(Not_tainted):Objects_remaining_in_hugetlbfs_inode_cache_on__kmem_cache_shutdown()

2018-01-17 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: c0033af7eec3e728c6b70d75950e632ace4c8a55 ("hugetlbfs: Convert to fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [kernfs, sysfs, cgroup, intel_rdt] 5aad045543: kernel_BUG_at_fs/super.c

2018-01-07 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 5aad04554302fc1fbb5924d0f8f68946ec5c06f7 ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context") https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context in testcase: trinity with following parameters:

[lkp-robot] [workqueue] 5c0338c687: blogbench.write_score -21.2% regression

2018-01-03 Thread kernel test robot
Greeting, FYI, we noticed a -21.2% regression of blogbench.write_score due to commit: commit: 5c0338c68706be53b3dc472e4308961c36e4ece1 ("workqueue: restore WQ_UNBOUND/max_active==1 to be ordered") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: blogbench

[lkp-robot] [perf machine] 8edf8850d5: stderr./usr/src/linux-perf-x86_64-rhel-#/tools/perf/util/rb_resort.h:#:#:error:passing_argument#of'threads_sorted__new'from_incompatible_pointer_type[-Werror=in

2018-01-03 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 8edf8850d51e911a35b5d7aad4f8604db11abc66 ("perf machine: Use cached rbtrees") url: https://github.com/0day-ci/linux/commits/Davidlohr-Bueso/tools-perf-Update-rbtree-implementation-and-optimize-users/20171128-120320 in testcase:

  1   2   3   4   5   6   7   >