Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Sergey Senozhatsky
On (11/30/17 16:07), Andrey Ryabinin wrote: [..] > >> You can try dirty patch from here: > >> https://groups.google.com/d/msg/kasan-dev/iDb5bhcMBT0/55QzwWaHAwAJ > >> It should make KASAN print the exact variable name and frame where it > >> was allocated. > > > > would be good if Fengguang can

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Sergey Senozhatsky
On (11/30/17 16:07), Andrey Ryabinin wrote: [..] > >> You can try dirty patch from here: > >> https://groups.google.com/d/msg/kasan-dev/iDb5bhcMBT0/55QzwWaHAwAJ > >> It should make KASAN print the exact variable name and frame where it > >> was allocated. > > > > would be good if Fengguang can

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Sergey Senozhatsky
On (11/30/17 22:30), Fengguang Wu wrote: > On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: > > On (11/30/17 09:16), Dmitry Vyukov wrote: > > [..] > > > > to be honest, this backtrace hardly makes any sense to me. > > > > > > > > vprintk_emit() > > > >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Sergey Senozhatsky
On (11/30/17 22:30), Fengguang Wu wrote: > On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: > > On (11/30/17 09:16), Dmitry Vyukov wrote: > > [..] > > > > to be honest, this backtrace hardly makes any sense to me. > > > > > > > > vprintk_emit() > > > >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Dmitry Vyukov
On Thu, Nov 30, 2017 at 3:30 PM, Fengguang Wu wrote: > On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: >> >> On (11/30/17 09:16), Dmitry Vyukov wrote: >> [..] >>> >>> > to be honest, this backtrace hardly makes any sense to me. >>> > >>> >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Dmitry Vyukov
On Thu, Nov 30, 2017 at 3:30 PM, Fengguang Wu wrote: > On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: >> >> On (11/30/17 09:16), Dmitry Vyukov wrote: >> [..] >>> >>> > to be honest, this backtrace hardly makes any sense to me. >>> > >>> > vprintk_emit() >>> >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Fengguang Wu
On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: On (11/30/17 09:16), Dmitry Vyukov wrote: [..] > to be honest, this backtrace hardly makes any sense to me. > > vprintk_emit() > reserve_standard_io_resources() > __flush_tlb_all() >vprintk_emit() >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Fengguang Wu
On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: On (11/30/17 09:16), Dmitry Vyukov wrote: [..] > to be honest, this backtrace hardly makes any sense to me. > > vprintk_emit() > reserve_standard_io_resources() > __flush_tlb_all() >vprintk_emit() >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Andrey Ryabinin
On 11/30/2017 11:29 AM, Sergey Senozhatsky wrote: > On (11/30/17 09:16), Dmitry Vyukov wrote: > [..] >>> to be honest, this backtrace hardly makes any sense to me. >>> >>> vprintk_emit() >>> reserve_standard_io_resources() >>> __flush_tlb_all() >>>vprintk_emit() >>>

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Andrey Ryabinin
On 11/30/2017 11:29 AM, Sergey Senozhatsky wrote: > On (11/30/17 09:16), Dmitry Vyukov wrote: > [..] >>> to be honest, this backtrace hardly makes any sense to me. >>> >>> vprintk_emit() >>> reserve_standard_io_resources() >>> __flush_tlb_all() >>>vprintk_emit() >>>

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Fengguang Wu
On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: On (11/30/17 09:16), Dmitry Vyukov wrote: [..] > to be honest, this backtrace hardly makes any sense to me. > > vprintk_emit() > reserve_standard_io_resources() > __flush_tlb_all() >vprintk_emit() >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Fengguang Wu
On Thu, Nov 30, 2017 at 05:29:09PM +0900, Sergey Senozhatsky wrote: On (11/30/17 09:16), Dmitry Vyukov wrote: [..] > to be honest, this backtrace hardly makes any sense to me. > > vprintk_emit() > reserve_standard_io_resources() > __flush_tlb_all() >vprintk_emit() >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Sergey Senozhatsky
On (11/30/17 09:16), Dmitry Vyukov wrote: [..] > > to be honest, this backtrace hardly makes any sense to me. > > > > vprintk_emit() > > reserve_standard_io_resources() > > __flush_tlb_all() > >vprintk_emit() > > __down_trylock_console_sem() > > wake_up_klogd() > >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Sergey Senozhatsky
On (11/30/17 09:16), Dmitry Vyukov wrote: [..] > > to be honest, this backtrace hardly makes any sense to me. > > > > vprintk_emit() > > reserve_standard_io_resources() > > __flush_tlb_all() > >vprintk_emit() > > __down_trylock_console_sem() > > wake_up_klogd() > >

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Dmitry Vyukov
.00]Tasks RCU enabled. >> [0.00] NR_IRQS: 4352, nr_irqs: 48, preallocated irqs: 16 >> [0.00] >> ================== >> [0.00] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0: &

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-30 Thread Dmitry Vyukov
. >> [0.00] NR_IRQS: 4352, nr_irqs: 48, preallocated irqs: 16 >> [0.00] >> ====================== >> [0.00] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0: >>

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-29 Thread Sergey Senozhatsky
ed irqs: 16 > [0.00] > ============== > [0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0: > atomic_read at > arch/x86/include/asm/atomic.h:27 >(inlined by) static_k

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-29 Thread Sergey Senozhatsky
ed irqs: 16 > [0.00] > ============== > [0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0: > atomic_read at > arch/x86/include/asm/atomic.h:27 >(inlined by) static_k

[ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-29 Thread Fengguang Wu
). [0.00] Tasks RCU enabled. [0.00] NR_IRQS: 4352, nr_irqs: 48, preallocated irqs: 16 [0.00] == [0.00] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

[ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

2017-11-29 Thread Fengguang Wu
). [0.00] Tasks RCU enabled. [0.00] NR_IRQS: 4352, nr_irqs: 48, preallocated irqs: 16 [0.00] == [0.00] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0