Re: [LKP] [rcu] kernel BUG at include/linux/pagemap.h:149!
by Frederic Weisbecker
On Fri, Sep 11, 2015 at 10:19:47AM +0800, Boqun Feng wrote:
> Subject: [PATCH 01/27] rcu: Don't disable preemption for Tiny and Tree RCU
> readers
>
> Because preempt_disable() maps to barrier() for non-debug builds,
> it forces the compiler to spill and reload registers. Because Tree
> RCU and Tiny RCU now only appear in CONFIG_PREEMPT=n builds, these
> barrier() instances generate needless extra code for each instance of
> rcu_read_lock() and rcu_read_unlock(). This extra code slows down Tree
> RCU and bloats Tiny RCU.
>
> This commit therefore removes the preempt_disable() and preempt_enable()
> from the non-preemptible implementations of __rcu_read_lock() and
> __rcu_read_unlock(), respectively.
>
> For debug purposes, preempt_disable() and preempt_enable() are still
> kept if CONFIG_PREEMPT_COUNT=y, which makes the detection of sleeping
> inside atomic sections still work in non-preemptible kernels.
>
> Signed-off-by: Boqun Feng <boqun.feng(a)gmail.com>
> Signed-off-by: Paul E. McKenney <paulmck(a)linux.vnet.ibm.com>
> ---
> include/linux/rcupdate.h | 6 ++++--
> include/linux/rcutiny.h | 1 +
> kernel/rcu/tree.c | 9 +++++++++
> 3 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
> index d63bb77..6c3cece 100644
> --- a/include/linux/rcupdate.h
> +++ b/include/linux/rcupdate.h
> @@ -297,12 +297,14 @@ void synchronize_rcu(void);
>
> static inline void __rcu_read_lock(void)
> {
> - preempt_disable();
> + if (IS_ENABLED(CONFIG_PREEMPT_COUNT))
> + preempt_disable();
preempt_disable() is a no-op when !CONFIG_PREEMPT_COUNT, right?
Or rather it's a barrier(), which is anyway implied by rcu_read_lock().
So perhaps we can get rid of the IS_ENABLED() check?
8 months, 3 weeks
Extending the 0-day system with syzkaller?
by David Drysdale
Hi Fengguang / LKP-folk,
Quick question -- how easy is it to add extra builds/tests/checks to
your marvellous 0-day kbuild system?
The reason I ask is that I've recently been exploring syzkaller [1],
which is a system call fuzzer written by some of my colleagues here at
Google (cc'ed). Although it's fairly new, it has uncovered a bunch of
kernel bugs already [2] so I wondered if it might be a good candidate
for inclusion in the 0-day checks at some point.
(As an aside, I'm in the process of writing an article about syzkaller
for LWN, which might also expose it to more folk.)
What do you think?
Thanks,
David
[1] https://github.com/google/syzkaller
[2] https://github.com/google/syzkaller/wiki/Found-Bugs
3 years, 8 months
[lkp] [ptrace] 63a745aa6a: inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git for-kbuild-bot/current-stable
commit 63a745aa6ac924a1dd17567e03bac83050afc8de ("ptrace: fix ptrace vs tasklist_lock race")
+-------------------------------------------------+------------+------------+
| | 722e07cda3 | 63a745aa6a |
+-------------------------------------------------+------------+------------+
| boot_successes | 52 | 27 |
| boot_failures | 0 | 6 |
| inconsistent{HARDIRQ-ON-W}->{IN-HARDIRQ-W}usage | 0 | 6 |
| backtrace:ptrace_check_attach | 0 | 6 |
| backtrace:SyS_ptrace | 0 | 6 |
| backtrace:cpu_startup_entry | 0 | 2 |
+-------------------------------------------------+------------+------------+
[ 29.600508] [ INFO: inconsistent lock state ]
[ 29.601341] 4.4.0-rc6-00128-g63a745a #1 Not tainted
[ 29.602035] ---------------------------------
[ 29.602667] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
[ 29.603480] swapper/1/0 [HC1[1]:SC0[0]:HE0:SE1] takes:
[ 29.604191] (&(&sighand->siglock)->rlock){?.+...}, at: [<ffffffff810e4d01>] __lock_task_sighand+0xb5/0x10a
[ 29.605813] {HARDIRQ-ON-W} state was registered at:
[ 29.606553] [<ffffffff811151e6>] mark_held_locks+0x5e/0x74
[ 29.607395] [<ffffffff81115340>] trace_hardirqs_on_caller+0x144/0x197
[ 29.608327] [<ffffffff811153a0>] trace_hardirqs_on+0xd/0xf
[ 29.609215] [<ffffffff82e30b3b>] _raw_spin_unlock_irq+0x2c/0x3b
[ 29.610149] [<ffffffff810e0fdb>] ptrace_check_attach+0xbc/0x147
[ 29.611038] [<ffffffff810e19a2>] SyS_ptrace+0x97/0xea
[ 29.611827] [<ffffffff82e314b2>] entry_SYSCALL_64_fastpath+0x12/0x76
[ 29.612807] irq event stamp: 160226
[ 29.613540] hardirqs last enabled at (160223): [<ffffffff8105f2e9>] default_idle+0x1f/0x37
[ 29.614821] hardirqs last disabled at (160224): [<ffffffff82e32267>] apic_timer_interrupt+0x87/0xa0
[ 29.616140] softirqs last enabled at (160226): [<ffffffff810dc633>] _local_bh_enable+0x42/0x44
[ 29.617461] softirqs last disabled at (160225): [<ffffffff810dd405>] irq_enter+0x2e/0x65
[ 29.618704]
[ 29.618704] other info that might help us debug this:
[ 29.619679] Possible unsafe locking scenario:
[ 29.619679]
[ 29.620598] CPU0
[ 29.621064] ----
[ 29.621482] lock(&(&sighand->siglock)->rlock);
[ 29.622311] <Interrupt>
[ 29.622747] lock(&(&sighand->siglock)->rlock);
[ 29.623562]
[ 29.623562] *** DEADLOCK ***
[ 29.623562]
[ 29.624603] 2 locks held by swapper/1/0:
[ 29.625274] #0: (rcu_read_lock){......}, at: [<ffffffff810e2df2>] rcu_read_lock+0x0/0x68
[ 29.626808] #1: (rcu_read_lock){......}, at: [<ffffffff810e2df2>] rcu_read_lock+0x0/0x68
[ 29.628333]
[ 29.628333] stack backtrace:
[ 29.629258] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.0-rc6-00128-g63a745a #1
[ 29.630352] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
[ 29.631563] 0000000000000000 ffff880034803c00 ffffffff8173e2ff ffff8800329d82c0
[ 29.632992] ffff880034803c50 ffffffff81114f72 0000000000000000 0000000000000000
[ 29.635104] 0000000000000001 0000000000000000 ffff8800329d8b60 ffffffff81114825
[ 29.637195] Call Trace:
[ 29.637910] <IRQ> [<ffffffff8173e2ff>] dump_stack+0x4b/0x63
[ 29.639263] [<ffffffff81114f72>] print_usage_bug+0x1ba/0x1cf
[ 29.640430] [<ffffffff81114825>] ? check_usage_backwards+0xba/0xba
[ 29.641721] [<ffffffff8111509a>] mark_lock+0x113/0x201
[ 29.642945] [<ffffffff8111598d>] __lock_acquire+0x343/0xdee
[ 29.644210] [<ffffffff810e4d01>] ? __lock_task_sighand+0xb5/0x10a
[ 29.645453] [<ffffffff81115a59>] ? __lock_acquire+0x40f/0xdee
[ 29.646649] [<ffffffff811167ce>] lock_acquire+0x10a/0x196
[ 29.647773] [<ffffffff811167ce>] ? lock_acquire+0x10a/0x196
[ 29.648952] [<ffffffff810e4d01>] ? __lock_task_sighand+0xb5/0x10a
[ 29.650180] [<ffffffff82e307d4>] _raw_spin_lock+0x34/0x6a
[ 29.651391] [<ffffffff810e4d01>] ? __lock_task_sighand+0xb5/0x10a
[ 29.652741] [<ffffffff810e4d01>] __lock_task_sighand+0xb5/0x10a
[ 29.654091] [<ffffffff810e4d88>] do_send_sig_info+0x32/0x72
[ 29.655338] [<ffffffff810e521a>] group_send_sig_info+0x4e/0x56
[ 29.656533] [<ffffffff810e5352>] kill_pid_info+0x44/0x63
[ 29.657621] [<ffffffff8113ad9b>] it_real_fn+0xf4/0xfd
[ 29.658726] [<ffffffff81139d2a>] __hrtimer_run_queues+0x172/0x32c
[ 29.660120] [<ffffffff8113aca7>] ? SyS_getitimer+0x74/0x74
[ 29.661422] [<ffffffff8113a32a>] hrtimer_interrupt+0x7d/0x149
[ 29.662736] [<ffffffff810868a9>] local_apic_timer_interrupt+0x4b/0x4e
[ 29.664183] [<ffffffff82e341e0>] smp_apic_timer_interrupt+0x2e/0x3e
[ 29.665581] [<ffffffff82e3226c>] apic_timer_interrupt+0x8c/0xa0
[ 29.666933] <EOI> [<ffffffff81092305>] ? native_safe_halt+0x6/0x8
[ 29.668441] [<ffffffff8105f2ee>] default_idle+0x24/0x37
[ 29.669674] [<ffffffff8105f93b>] arch_cpu_idle+0xf/0x11
[ 29.670930] [<ffffffff8110d1c0>] default_idle_call+0x28/0x2f
[ 29.672242] [<ffffffff8110d39b>] cpu_startup_entry+0x17a/0x29a
[ 29.673526] [<ffffffff81085757>] start_secondary+0xe0/0xe3
[ 30.393040] trinity-main (852) used greatest stack depth: 12576 bytes left
[ 35.497090] random: nonblocking pool is initialized
[ 73.263306] init: Failed to create pty - disabling logging for job
Thanks,
Ying Huang
4 years, 1 month
[lkp] [selinux] 5d226df4ed: -10.1% unixbench.score
by kernel test robot
FYI, we noticed the below changes on
git://git.infradead.org/users/pcmoore/selinux stable-4.5
commit 5d226df4edfa0eb1e689e7ac2741cf261ff7cbf1 ("selinux: Revalidate invalid inode security labels")
=========================================================================================
compiler/cpufreq_governor/kconfig/nr_task/rootfs/tbox_group/test/testcase:
gcc-4.9/performance/x86_64-rhel/1/debian-x86_64-2015-02-07.cgz/ivb42/pipe/unixbench
commit:
6f3be9f562e3027c77bc4482ccf2cea8600a7f74
5d226df4edfa0eb1e689e7ac2741cf261ff7cbf1
6f3be9f562e3027c 5d226df4edfa0eb1e689e7ac27
---------------- --------------------------
%stddev %change %stddev
\ | \
2086 ± 0% -10.1% 1876 ± 0% unixbench.score
7.79 ± 0% -10.2% 7.00 ± 1% time.user_time
33404 ±117% +9470.5% 3196941 ±173% latency_stats.max.wait_on_page_bit.__filemap_fdatawait_range.filemap_fdatawait_keep_errors.sync_inodes_sb.sync_inodes_one_sb.iterate_supers.sys_sync.entry_SYSCALL_64_fastpath
18934 ± 34% -82.8% 3252 ± 73% latency_stats.sum.rpc_wait_bit_killable.__rpc_execute.rpc_execute.rpc_run_task.nfs4_call_sync_sequence.[nfsv4]._nfs4_proc_access.[nfsv4].nfs4_proc_access.[nfsv4].nfs_do_access.nfs_permission.__inode_permission.inode_permission.link_path_walk
57519 ±100% +5478.5% 3208706 ±172% latency_stats.sum.wait_on_page_bit.__filemap_fdatawait_range.filemap_fdatawait_keep_errors.sync_inodes_sb.sync_inodes_one_sb.iterate_supers.sys_sync.entry_SYSCALL_64_fastpath
13414 ± 33% +49.4% 20036 ± 8% numa-meminfo.node0.Active(anon)
13399 ± 33% +49.0% 19963 ± 7% numa-meminfo.node0.AnonPages
11624 ± 38% -52.7% 5495 ± 18% numa-meminfo.node1.Active(anon)
11518 ± 38% -52.6% 5457 ± 17% numa-meminfo.node1.AnonPages
1641 ± 50% -53.8% 757.75 ± 15% numa-meminfo.node1.PageTables
3353 ± 33% +49.2% 5004 ± 8% numa-vmstat.node0.nr_active_anon
3349 ± 33% +49.0% 4991 ± 7% numa-vmstat.node0.nr_anon_pages
2904 ± 38% -52.7% 1374 ± 18% numa-vmstat.node1.nr_active_anon
2878 ± 38% -52.6% 1365 ± 17% numa-vmstat.node1.nr_anon_pages
410.00 ± 50% -53.9% 189.00 ± 15% numa-vmstat.node1.nr_page_table_pages
14760 ± 2% +207.2% 45336 ± 65% numa-vmstat.node1.numa_other
ivb42: Ivytown Ivy Bridge-EP
Memory: 64G
unixbench.score
2150 ++-------------------------------------------------------------------+
| |
2100 ++ .*..*.*.. |
| .*..* *.*..*. .*.*..*.* |
*.*..*.*..* *..*.*.*..*.*..*.*. |
2050 ++ |
| |
2000 ++ |
| |
1950 ++ |
| |
O O O O O O O O O O O O O O |
1900 ++ O O O O O O O O O O O |
| O O O O
1850 ++-------------------------------------------------------------------+
[*] bisect-good sample
[O] bisect-bad sample
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Ying Huang
4 years, 1 month
[lkp] [f2fs] 75cd4e098d: xfstests.generic.042.fail
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 75cd4e098d178433436abce08146a21647bb4585 ("f2fs: support FALLOC_FL_ZERO_RANGE")
We found after your commit, the xfstests test case 009/042 failed.
=========================================================================================
compiler/disk/fs/kconfig/rootfs/tbox_group/test/testcase:
gcc-4.9/4HDD/f2fs/x86_64-rhel/debian-x86_64-2015-02-07.cgz/vm-kbuild-4G/generic-quick/xfstests
commit:
b4ace33703243fed56f8bfc80a001533acb9decb
75cd4e098d178433436abce08146a21647bb4585
b4ace33703243fed 75cd4e098d178433436abce081
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:18 94% 17:18 xfstests.generic.009.fail
:18 94% 17:18 xfstests.generic.042.fail
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Ying Huang
4 years, 1 month
[lkp] [net] 9dc0990f12: INFO: suspicious RCU usage. ]
by kernel test robot
FYI, we noticed the below changes on
https://github.com/0day-ci/linux John-Fastabend/drop-the-qdisc-lock-for-pfifo_fast-mq/20151231-015853
commit 9dc0990f12fb6ba8e32a63578aa060408958595a ("net: sched: pfifo_fast new option to deque multiple pkts")
With your commit, there is the following new message in kernel log.
Please take a look at the attached dmesg for details.
[ 87.658006] IP-Config: Reopening network devices...
Thanks,
Ying Huang
4 years, 1 month
[lkp] [kernel/*] c7af9d5728: BUG kmalloc-16 (Not tainted): Invalid object pointer 0xd5c76188
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
commit c7af9d5728bed29ef614324e67e066896d087c8f ("kernel/*: switch to memdup_user_nul()")
[ 5.642811] init: Failed to create pty - disabling logging for job
[ 5.644294] init: Temporary process spawn error: No such file or directory
[ 5.647068] =============================================================================
[ 5.648682] BUG kmalloc-16 (Not tainted): Invalid object pointer 0xd5c76188
[ 5.650210] -----------------------------------------------------------------------------
[ 5.650210]
[ 5.652968] INFO: Slab 0xd4dd9270 objects=21 used=16 fp=0xd5c763c0 flags=0x40000081
[ 5.661970] init: Failed to create pty - disabling logging for job
[ 5.672197] init: Failed to create pty - disabling logging for job
[ 5.676338] FIX kmalloc-16: Object at 0xd5c76188 not freed
[ 5.682358] init: Failed to create pty - disabling logging for job
[ 5.689500] init: Failed to create pty - disabling logging for job
[ 5.691245] =============================================================================
[ 5.692985] BUG kmalloc-8 (Tainted: G B ): Invalid object pointer 0xd6331daa
[ 5.694699] -----------------------------------------------------------------------------
[ 5.694699]
[ 5.697562] INFO: Slab 0xd4de9fa8 objects=22 used=21 fp=0xd6331228 flags=0x40000081
[ 5.716715] init: Failed to create pty - disabling logging for job
[ 5.724667] init: Failed to create pty - disabling logging for job
[ 5.729182] FIX kmalloc-8: Object at 0xd6331daa not freed
[ 5.735529] =============================================================================
[ 5.737191] BUG kmalloc-8 (Tainted: G B ): Invalid object pointer 0xd5c6622a
[ 5.738862] -----------------------------------------------------------------------------
[ 5.738862]
[ 5.741627] INFO: Slab 0xd4dd8ff0 objects=22 used=21 fp=0xd5c66da8 flags=0x40000081
[ 5.751525] FIX kmalloc-8: Object at 0xd5c6622a not freed
[ 5.753196] =============================================================================
[ 5.754916] BUG kmalloc-8 (Tainted: G B ): Invalid object pointer 0xd5c3cace
[ 5.756615] -----------------------------------------------------------------------------
[ 5.756615]
[ 5.759498] INFO: Slab 0xd4dd8960 objects=22 used=22 fp=0x (null) flags=0x40000081
[ 5.787040] FIX kmalloc-8: Object at 0xd5c3cace not freed
[ 5.899620] init: Failed to create pty - disabling logging for job
[ 5.902464] init: Failed to create pty - disabling logging for job
Thanks,
Kernel Test Robot
4 years, 1 month
[lkp] [x86,vdso] 6c5548f6d7: autotest.signaltest.fail
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/vdso
commit 6c5548f6d716edd2e88add5e7826d15acae30108 ("x86,vdso: Use .fault instead of remap_pfn_range for the vvar mapping")
2015-12-28 18:41:40 client/autotest-local run signaltest
18:41:40 INFO | Writing results to /lkp/benchmarks/autotest/client/results/default
18:41:40 ERROR| Could not determine initlevel, assuming 2
18:41:40 INFO | START ---- ---- timestamp=1451299300 localtime=Dec 28 18:41:40
18:41:40 INFO | START signaltest signaltest timestamp=1451299300 localtime=Dec 28 18:41:40
18:41:41 WARNI| Could not find GDB installed. Crash handling will operate with limited functionality
18:41:41 ERROR| [stderr] signaltest.c: In function 'signalthread':
18:41:41 ERROR| [stderr] signaltest.c:133:27: warning: null argument where non-null required (argument 1) [-Wnonnull]
18:41:41 ERROR| [stderr] gettimeofday(0,(struct timezone *)1);
18:41:41 ERROR| [stderr] ^
18:41:41 ERROR| [stderr] signaltest.c:179:5: warning: null argument where non-null required (argument 1) [-Wnonnull]
18:41:41 ERROR| [stderr] gettimeofday(0,0);
18:41:41 ERROR| [stderr] ^
18:41:41 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/lkp/benchmarks/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/lkp/benchmarks/autotest/client/shared/test.py", line 823, in _call_test_function
return func(*args, **dargs)
File "/lkp/benchmarks/autotest/client/tests/signaltest/signaltest.py", line 19, in execute
utils.system(self.srcdir + '/signaltest ' + args)
File "/lkp/benchmarks/autotest/client/shared/utils.py", line 1230, in system
verbose=verbose).exit_status
File "/lkp/benchmarks/autotest/client/shared/utils.py", line 916, in run
"Command returned non-zero exit status")
CmdError: Command </lkp/benchmarks/autotest/client/tmp/signaltest/src/signaltest -t 10 -l 100000> failed, rc=-7, Command returned non-zero exit status
* Command:
/lkp/benchmarks/autotest/client/tmp/signaltest/src/signaltest -t 10 -l
100000
Exit status: -7
Duration: 0.0431470870972
18:41:41 WARNI| Programs crashed during test execution
18:41:41 WARNI| Please verify /lkp/benchmarks/autotest/client/results/default/signaltest/debug/crash.signaltest.814 for more info
18:41:41 INFO | System log file not found (looked for ['/var/log/messages', '/var/log/syslog'])
18:41:41 ERROR| child process failed
18:41:41 INFO | ERROR signaltest signaltest timestamp=1451299301 localtime=Dec 28 18:41:41 Command </lkp/benchmarks/autotest/client/tmp/signaltest/src/signaltest -t 10 -l 100000> failed, rc=-7, Command returned non-zero exit status
* Command:
/lkp/benchmarks/autotest/client/tmp/signaltest/src/signaltest -t 10 -l
100000
Exit status: -7
Duration: 0.0431470870972
18:41:41 INFO | END ERROR signaltest signaltest timestamp=1451299301 localtime=Dec 28 18:41:41
18:41:41 INFO | END GOOD ---- ---- timestamp=1451299301 localtime=Dec 28 18:41:41
18:41:41 INFO | Report successfully generated at /lkp/benchmarks/autotest/client/results/default/job_report.html
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Ying Huang
4 years, 1 month
[lkp] [x86/mm] 48913aacc7: BUG: KASAN: stack-out-of-bounds in reserve_bootmem_region+0x7e/0x92 at addr ffffea00000cfce8
by kernel test robot
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/pcid
commit 48913aacc754c8ed74a4ffb4f97dc4c1462106ff ("x86/mm: If INVPCID is available, use it to flush global mappings")
+----------------+------------+------------+
| | a36de2a72b | 48913aacc7 |
+----------------+------------+------------+
| boot_successes | 63 | 0 |
+----------------+------------+------------+
[ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.000000] ==================================================================
[ 0.000000] BUG: KASAN: stack-out-of-bounds in reserve_bootmem_region+0x7e/0x92 at addr ffffea00000cfce8
[ 0.000000] Write of size 8 by task swapper/0
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.0-rc5-00003-g48913aa #3
[ 0.000000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
[ 0.000000] 0000000000000000 ffffffff83ec7d20 ffffffff83630136 1ffffd4000019f9d
[ 0.000000] ffffffff83ec7d98 ffffffff833d61c4 ffffffff843106e4 0000000000000082
[ 0.000000] 0000000000000000 ffffffff8428d680 ffffffff83ec7d60 ffffffff8321a8bf
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff83630136>] dump_stack+0x4b/0x6c
[ 0.000000] [<ffffffff833d61c4>] kasan_report+0x347/0x48b
[ 0.000000] [<ffffffff843106e4>] ? reserve_bootmem_region+0x7e/0x92
[ 0.000000] [<ffffffff8321a8bf>] ? wrmsrl+0x10/0x12
[ 0.000000] [<ffffffff833d5608>] __asan_store8+0x26/0x68
[ 0.000000] [<ffffffff843106e4>] reserve_bootmem_region+0x7e/0x92
[ 0.000000] [<ffffffff842e9ea7>] free_all_bootmem+0xdb/0x1d0
[ 0.000000] [<ffffffff842e9dcc>] ? reset_all_zones_managed_pages+0x3e/0x3e
[ 0.000000] [<ffffffff842ccf18>] ? sort_iommu_table+0x8c/0x106
[ 0.000000] [<ffffffff842cce8c>] ? find_dependents_of+0x59/0x59
[ 0.000000] [<ffffffff842dc21b>] ? add_pcspkr+0xae/0xae
[ 0.000000] [<ffffffff842dc299>] ? pci_xen_swiotlb_detect+0x8/0x8
[ 0.000000] [<ffffffff842dc2c6>] ? pci_swiotlb_init+0x2d/0x2d
[ 0.000000] [<ffffffff842cce6e>] ? find_dependents_of+0x3b/0x59
[ 0.000000] [<ffffffff842cd01c>] ? check_iommu_entries+0x8a/0xd3
[ 0.000000] [<ffffffff842dd2d0>] mem_init+0xe/0x4a
[ 0.000000] [<ffffffff842c4f6e>] start_kernel+0x2d3/0x522
[ 0.000000] [<ffffffff842c4c9b>] ? thread_info_cache_init+0x6/0x6
[ 0.000000] [<ffffffff84312aa1>] ? memblock_reserve+0x4a/0x4f
[ 0.000000] [<ffffffff842c4120>] ? early_idt_handler_array+0x120/0x120
[ 0.000000] [<ffffffff842c4120>] ? early_idt_handler_array+0x120/0x120
[ 0.000000] [<ffffffff842c4328>] x86_64_start_reservations+0x2a/0x2c
[ 0.000000] [<ffffffff842c443e>] x86_64_start_kernel+0x114/0x121
[ 0.000000] Memory state around the buggy address:
[ 0.000000] ffffea00000cfb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 0.000000] ffffea00000cfc00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Thanks,
Kernel Test Robot
4 years, 1 month
