Re: Question on KASAN calltrace record in RT

2021-04-15 Thread Mike Galbraith
On Wed, 2021-04-14 at 07:26 +0200, Dmitry Vyukov wrote: > > > [ 15.428008] > > == > > [ 15.428011] BUG: KASAN: vmalloc-out-of-bounds in > > crash_setup_memmap_entries+0x17e/0x3a0 > > This looks like a genuine kernel bug on first

回复: 回复: Question on KASAN calltrace record in RT

2021-04-14 Thread Zhang, Qiang
KASAN calltrace record in RT [Please note: This e-mail is from an EXTERNAL e-mail address] On Wed, 2021-04-14 at 07:29 +, Zhang, Qiang wrote: > > if CONFIG_PREEMPT_RT is enabled and but not in preemptible, the prealloc > should be allowed > >No, you can't take an rtmutex

Re: 回复: Question on KASAN calltrace record in RT

2021-04-14 Thread Mike Galbraith
On Wed, 2021-04-14 at 07:29 +, Zhang, Qiang wrote: > > if CONFIG_PREEMPT_RT is enabled and but not in preemptible, the prealloc > should be allowed No, you can't take an rtmutex when not preemptible. -Mike

回复: Question on KASAN calltrace record in RT

2021-04-14 Thread Zhang, Qiang
calltrace record in RT [Please note: This e-mail is from an EXTERNAL e-mail address] On Tue, 2021-04-13 at 17:29 +0200, Dmitry Vyukov wrote: > On Tue, Apr 6, 2021 at 10:26 AM Zhang, Qiang > wrote: > > > > Hello everyone > > > > In RT system, after Andrew test,

Re: Question on KASAN calltrace record in RT

2021-04-14 Thread Dmitry Vyukov
el@vger.kernel.org; > kasan-...@googlegroups.com > 主题: Re: Question on KASAN calltrace record in RT > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > On Tue, Apr 6, 2021 at 10:26 AM Zhang, Qiang > wrote: > > > > Hello everyone > > > > In R

回复: Question on KASAN calltrace record in RT

2021-04-13 Thread Zhang, Qiang
发件人: Dmitry Vyukov 发送时间: 2021年4月13日 23:29 收件人: Zhang, Qiang 抄送: Andrew Halaney; andreyk...@gmail.com; ryabinin@gmail.com; a...@linux-foundation.org; linux-kernel@vger.kernel.org; kasan-...@googlegroups.com 主题: Re: Question on KASAN calltrace record

Re: Question on KASAN calltrace record in RT

2021-04-13 Thread Mike Galbraith
On Wed, 2021-04-14 at 07:26 +0200, Dmitry Vyukov wrote: > On Wed, Apr 14, 2021 at 6:00 AM Mike Galbraith wrote: > > > [0.692437] BUG: sleeping function called from invalid context at > > kernel/locking/rtmutex.c:943 > > [0.692439] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1,

Re: Question on KASAN calltrace record in RT

2021-04-13 Thread Dmitry Vyukov
On Wed, Apr 14, 2021 at 6:00 AM Mike Galbraith wrote: > > On Tue, 2021-04-13 at 17:29 +0200, Dmitry Vyukov wrote: > > On Tue, Apr 6, 2021 at 10:26 AM Zhang, Qiang > > wrote: > > > > > > Hello everyone > > > > > > In RT system, after Andrew test, found the following calltrace , > > > in KASA

Re: Question on KASAN calltrace record in RT

2021-04-13 Thread Mike Galbraith
On Tue, 2021-04-13 at 17:29 +0200, Dmitry Vyukov wrote: > On Tue, Apr 6, 2021 at 10:26 AM Zhang, Qiang > wrote: > > > > Hello everyone > > > > In RT system, after Andrew test, found the following calltrace , > > in KASAN, we record callstack through stack_depot_save(), in this function, > >

Re: Question on KASAN calltrace record in RT

2021-04-13 Thread Dmitry Vyukov
On Tue, Apr 6, 2021 at 10:26 AM Zhang, Qiang wrote: > > Hello everyone > > In RT system, after Andrew test, found the following calltrace , > in KASAN, we record callstack through stack_depot_save(), in this function, > may be call alloc_pages, but in RT, the spin_lock replace with > rt_mut

Question on KASAN calltrace record in RT

2021-04-06 Thread Zhang, Qiang
Hello everyone In RT system, after Andrew test, found the following calltrace , in KASAN, we record callstack through stack_depot_save(), in this function, may be call alloc_pages, but in RT, the spin_lock replace with rt_mutex in alloc_pages(), if before call this function, the irq is dis