FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
wb-buf-throttle
commit 93408371951a8c076c58a532e3e7e14969e5e015 ("writeback: throttle buffered
writeback")
in testcase: boot
on test machine: 1 threads qemu-system-x86_64 -enable-kvm -c
6_64-9 -serial
file:/dev/shm/kboot/serial-vm-lkp-wsx03-quantal-x86_64-9 -daemonize -display
none -monitor null
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.7.0-rc6 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_I
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
Deepa-Dinamani/Delete-CURRENT_TIME-and-CURRENT_TIME_SEC-macros/20160620-104147
commit c43edc7bd9c06af9a7278101d462eb0ba0299605 ("fs: Replace CURRENT_TIME with
current_time() for inode timestamps")
on test machine: vm-kbuil
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git x86
commit 19fa5e73647fde1e6a7038a8f05cddf4c43f08d3 ("x86 tsc: enumerate SKL
cpu_khz and tsc_khz via CPUID")
on test machine: vm-kbuild-yocto-x86_64: 1 threads qemu-system-x86_64
-enable-kvm -
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
Wang-Shilong/jbd2-wake-up-j_wait_done_commit-before-commit-callback/20160616-115406
commit 41f6316ed374dba6f9693d917c1815019f075bdf ("jbd2: wake up
j_wait_done_commit before commit callback")
in testcase: ext4-frags
with fo
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
wb-buf-throttle
commit c284d3afba4e7f6a18122b416daceb994412ed6d ("writeback: throttle buffered
writeback")
in testcase: boot
on test machine: 1 threads qemu-system-x86_64 -enable-kvm -c
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git blk-dio
commit 9f9093afaff2c4d247e5bc7d25ec0574e3f8d12b ("blk-mq: private O_DIRECT
implementation")
in testcase: boot
on test machine: 2 threads qemu-system-x86_64 -enable-kvm -cpu
Hasw
14.569443] [] ? rest_init+0x2df/0x2df
[ 14.581955] ima: No TPM chip found, activating TPM-bypass!
[ 14.582650] evm: HMAC attrs: 0x1
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.8.0-rc1 Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CO
14.569443] [] ? rest_init+0x2df/0x2df
[ 14.581955] ima: No TPM chip found, activating TPM-bypass!
[ 14.582650] evm: HMAC attrs: 0x1
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.8.0-rc1 Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CO
14.569443] [] ? rest_init+0x2df/0x2df
[ 14.581955] ima: No TPM chip found, activating TPM-bypass!
[ 14.582650] evm: HMAC attrs: 0x1
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.8.0-rc1 Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CO
14.569443] [] ? rest_init+0x2df/0x2df
[ 14.581955] ima: No TPM chip found, activating TPM-bypass!
[ 14.582650] evm: HMAC attrs: 0x1
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.8.0-rc1 Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CO
32.225846] ---[ end trace 8f84425f8176b010 ]---
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.8.0-rc5 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
cheng-chao/sched-core-simpler-function-for-sched_exec-migration/20160905-142452
commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2 ("sched/core: simpler function
for sched_exec migration")
in testcase: trinity
with following p
t+0x9/0xf0
[1.047061] [] ret_from_fork+0x1f/0x40
[1.047670] [] ? rest_init+0xc0/0xc0
Elapsed time: 10
Thanks,
Kernel Test Robot
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.8.0-rc1 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION
able+0x3f0/0x4a3
[ 251.080939] [] kernel_init+0xc/0x105
[ 251.092221] [] ret_from_fork+0x1f/0x40
[ 251.103790] [] ? rest_init+0xe8/0xe8
[ 251.131376] ima: No TPM chip found, activating TPM-bypass!
[ 251.154124] raid6test: testing the 4-disk case...
Thanks,
Kernel Test Robot
#
# Aut
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
Nicholas-Krause/fs-Fix-kmemleak-leak-warning-in-getname_flags-about-working-on-unitialized-memory/20160804-055054
commit 45ec18d5c713bccb9807782f0dca29b92ba99784 ("fs:Fix kmemleak leak warning
in getname_flags about working
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
kan-liang-intel-com/net-introduce-NET-policy/20160805-034810
commit ed519e02592874e3cb2d643173e9f34bee2d74e7 ("net/netpolicy: fast path for
finding the queues")
in testcase: boot
on test machine: 2 threads qemu-system-i386
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
David-Carrillo-Cisneros/remove-unnecessary-IPI-reading-uncore-events/20160802-124051
commit 34ab11270a27536c1d4ff3d5bb7ae9d58daa016c ("perf/core: introduce
pmu_event_flags and PMUEF_READ_CPU_PKG")
in testcase: boot
on test
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
Waiman-Long/locking-rwsem-Enable-reader-optimistic-spinning/20160819-150117
commit 1802442a39b862b1adb57cbae5fbbda3945406e2 ("locking/rwsem: Add a boot
parameter to reader spinning threshold")
in testcase: boot
on test mac
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 locking/core
commit d0541b0fa64b36665d6261079974a26943c75009
Author: Byungchul Park
AuthorDate: Thu Aug 17 17:57:39 2017 +0900
Commit: Ingo Mo
FYI, we noticed the following commit:
commit: 1be7107fbe18eed3e319a6c3e83c78254b693acb ("mm: larger stack guard gap,
between vmas")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
with following parameters:
runtime: 300s
test-description: Tr
FYI, we noticed the following commit (built with gcc-4.9):
commit: 7f7c60e0663645e757e520245606fde9c6e326bb ("printk: hash addresses
printed with %p")
url:
https://github.com/0day-ci/linux/commits/Tobin-C-Harding/printk-hash-addresses-printed-with-p/20171024-231922
in testcase: trinity
with f
FYI, we noticed the following commit (built with gcc-6):
commit: 66688e9d11455f15983d08e7c14733969cd25919 ("x86/entry/64: Create a
percpu SYSCALL entry trampoline")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip
in testcase: boot
on test machine: qemu-system-x8
FYI, we noticed the following commit (built with gcc-6):
commit: e04a713254ef50629d1ae9558ddd4c118b7cb807 ("x86/asm/64: Use a percpu
trampoline stack for IDT entries")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip
in testcase: boot
on test machine: qemu-system
FYI, we noticed the following commit (built with gcc-6):
commit: 7b1f0050e45387563fb77c5ee18270567573b590 ("x86/asm/64: Use a percpu
trampoline stack for IDT entries")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip
in testcase: boot
on test machine: qemu-system
FYI, we noticed the following commit (built with gcc-4.9):
commit: 6ba0c46abfbfb7f68c34cfb23b042e74e765edbb ("x86/entry/64: Create a
percpu SYSCALL entry trampoline")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip
in testcase: trinity
with following parameters:
FYI, we noticed the following commit (built with gcc-4.9):
commit: b664d57f39d01e775204d4f1a7e2f8bda77bc549 ("kprobes/x86: Remove IRQ
disabling from jprobe handlers")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64 -e
FYI, we noticed the following commit (built with gcc-4.9):
commit: 0b00de857a648dafe7020878c7a27cf776f5edf4 ("x86/cpuid: Add generic table
for CPUID dependencies")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/fpu
in testcase: trinity
with following parameters:
runtime:
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 9c2fb296dde16a1bb81277be7b32cec881fe1153
Author: Kees Cook
AuthorDate: Mon Oct 16 20:01:58 2017 +0100
Commit: Mark Brown
FYI, we noticed the following commit (built with gcc-5):
commit: 2dcd5adfb7401b762ddbe4b86dcacc2f3de6b97b ("locking/lockdep: Remove the
BROKEN flag from CONFIG_LOCKDEP_CROSSRELEASE and CONFIG_LOCKDEP_COMPLETIONS")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git locking/core
in testcase
FYI, we noticed the following commit (built with gcc-5):
commit: eb948c71f790f4fd27440895ca19180a78fd3016 ("proc: mm: export PTE sizes
directly in smaps")
url:
https://github.com/0day-ci/linux/commits/Fan-Du/proc-mm-export-PTE-sizes-directly-in-smaps/20171027-233355
in testcase: trinity
with
FYI, we noticed the following commit (built with gcc-6):
commit: 45d87f5bb794a19baa7f92fdf2fabdcb0575c66d ("x86/topology: Avoid wasting
128k for package id array")
url:
https://github.com/0day-ci/linux/commits/Prarit-Bhargava/perf-x86-intel-uncore-Cache-logical-pkg-id-in-uncore-driver/20171027-
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git master
commit 81c72584a480c5a4b7eede527d0b990c83c2dcc9 ("mm: gup: make
get_user_pages_fast and __get_user_pages_fast latency conscious")
===
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 048883e0b934d9a5103d40e209cb14b7f33d2933 ("nfs: fix pg_test page count
calculation")
=
tb
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 15bec0ff5a9ba6d203178fa8772259df6207942a ("f2fs: do not skip dentry
block writes")
=
tbo
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 46cfb125d673f2f30acf06b3c02485bf693d54e9 ("mm: increase SWAP_CLUSTER_MAX
to batch TLB flushes")
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-pkeys.git
pkeys-v005-protsyscalls
commit 2205cb3c40c2ba6521427c9f8f36b2d4f2f2a98d ("x86, pkeys: arch-specific
protection bits")
===
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/strings
commit 3fda0fa0f5ed4ef634e043c65709482aea0a37f6 ("string: Improve the generic
strlcpy() implementation")
+--++---
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit b52da86e0ad58f096710977fcda856fd84da9233 ("sched/numa: Fix
task_tick_fair() from disabling numa_balancing")
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Shashank-Sharma/Color-Management-for-DRM-framework/20151020-202959
commit 6a9b928d4149ae2b195a2c13d55bf9c59a98c40c ("drm: Create Color Management
query properties")
+--
FYI, we noticed the below changes on
git://linuxtv.org/hverkuil/media_tree.git sdrout
commit bcd56c567886b1ff0d2569d9cfe056ebbdad59c1 ("vivid: wip for sdr output")
[ 123.619858] evbug: Connected device: input1 (AT Translated Set 2 keyboard at
isa0060/serio0/input0)
[ 123.662942] isa i2c-pca-i
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Shashank-Sharma/Color-Management-for-DRM/20151013-203652
commit 0e94a0bada080cd3c0d4d2516ef19a30064de1e0 ("drm: Create Color Management
query properties")
+--+-
FYI, we noticed the below changes on
https://github.com/pantoniou/linux-beagle-track-mainline.git bbb-overlays
commit db59ef4cdc3261322ea61686e714b571ef709484 ("of: unittest: Unit-tests for
target root overlays.")
We found some OF unittests errors in kernel log, while the line marked
with + is n
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:
r
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:
runtim
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: qemu-syst
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 2
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 -enable-k
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: Linus
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 -enable-kv
FYI, we noticed the following commit (built with gcc-4.9):
commit: 3f96d20fafb19e6dd869362ace53662b06e6f6c1 ("[PATCH] debugobjects:
Disable lockdep tracking of debugobjects internal locks")
url:
https://github.com/0day-ci/linux/commits/Waiman-Long/debugobjects-Disable-lockdep-tracking-of-debugo
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:
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 testc
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
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: qemu-system
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: qemu-sys
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: boot
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 H
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 -smp
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:
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
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
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 avoids ta
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
test-descri
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
test-descri
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
test-
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 set
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: Trin
FYI, we noticed the following commit (built with gcc-7):
commit: b1ff47aacea95e5be1bedf2aee740395b52f4591 ("[PATCH 5/5] x86/kernel:
jump_table: use relative references")
url:
https://github.com/0day-ci/linux/commits/Ard-Biesheuvel/add-support-for-relative-references-in-jump-tables/20180628-0212
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: Linu
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 M
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
t
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:
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
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
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:
runtime
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
FYI, we noticed the following commit (built with gcc-7):
commit: 2d251ff6e66d7978b3e7a9c69e99b7150de26926 ("mm, oom: fix unnecessary
killing of additional processes")
url:
https://github.com/0day-ci/linux/commits/David-Rientjes/mm-oom-fix-unnecessary-killing-of-additional-processes/20180527-033
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:
https://github.com/0day-ci/linux/commits/Paul-E-McKenney/RCU-consolidation-patches/2018
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:
https://github.com/0day-ci/linux/commits/Sandipan-Das/perf-tests-Fix-regex-for-record-probe_libc_inet_pton-sh/20180
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 testca
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:
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:
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: https://git
FYI, we noticed the following commit (built with gcc-7):
commit: 93eb07f72c8d86f8fe5e90907df1cc037f6ffbb7 ("xarray: Move
multiorder_shrink to kernel tests")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
with following parameters:
runtime: 30
FYI, we noticed the following commit (built with gcc-7):
commit: ec7d9c9ce897174243af4fcd201dbfc34df0f3a3 ("ide: replace ->proc_fops
with ->proc_show")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: rcutorture
with following parameters:
runtime: 300
FYI, we noticed the following commit (built with gcc-7):
commit: 641fb0efbff063ed57f108c2eb4a4d26dbd5badd ("iommu/of: Don't call
iommu_ops->add_device directly")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
with following parameters:
runt
FYI, we noticed the following commit (built with gcc-6):
commit: cbc815d9ce7ae30677c929e94b2e176d5f4a5a36 ("vfs: Simplify security mount
option processing")
https://git.kernel.org/cgit/linux/kernel/git/ebiederm/user-namespace.git
mount-cleanups-testing
in testcase: trinity
with following param
FYI, we noticed the following commit (built with gcc-6):
commit: 461e557b97277b693cd8008c32a9d01c7f8f453b ("rtc: nvmem: use
devm_nvmem_register()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
with following parameters:
runtime: 300s
tes
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
debugfs_cleanup
commit 1aba551c73de605983515118d5ad527594440ccb
Author: Greg Kroah-Hartman
AuthorDate: Fri Jan 4 14:06:22 2019 +0100
C
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 bea5b158ff0da9c7246ff391f754f5f38e34577a
Author: Rob Herring
AuthorDate: Thu Aug 11 10:20:58 2016 -0500
Commit: Greg Kroa
FYI, we noticed the following commit (built with gcc-4.9):
commit: b803b42823d0d9e8b6deccf01ffc2aba5d0738df ("xarray: Add XArray
iterators")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
with following parameters:
runtime: 300s
test-descri
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 R
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 -
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. M
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
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
test-
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 O
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:
https://github.com/0day-ci/linux/commits/Thomas-Gleixner/x86-mm-cpa-Improve-large-page-preservation-handling/2018
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
UPDATE-20180916-004446/Thomas-Gleixner/x86-mm-cpa-Improve-large-page-preservation-handling/20180915-
1 - 100 of 6599 matches
Mail list logo
