On Mon, Aug 21, 2017 at 01:58:13PM +0530, Shubham Bansal wrote:
> > This is a WARN, printk is a pig.
>
> So, its not a bug?
No, triggering the WARN is the problem, this is just fallout after that.
On Mon, Aug 21, 2017 at 01:58:13PM +0530, Shubham Bansal wrote:
> > This is a WARN, printk is a pig.
>
> So, its not a bug?
No, triggering the WARN is the problem, this is just fallout after that.
> This is a WARN, printk is a pig.
So, its not a bug?
> This is a WARN, printk is a pig.
So, its not a bug?
On Mon, Aug 21, 2017 at 01:56:27AM +0530, Shubham Bansal wrote:
> -> #1 ((console_sem).lock){..}:
>lock_acquire+0x173/0x470
>_raw_spin_lock_irqsave+0x42/0x60
>down_trylock+0x13/0x70
>__down_trylock_console_sem+0x38/0xc0
>console_trylock+0x17/0xb0
>
On Mon, Aug 21, 2017 at 01:56:27AM +0530, Shubham Bansal wrote:
> -> #1 ((console_sem).lock){..}:
>lock_acquire+0x173/0x470
>_raw_spin_lock_irqsave+0x42/0x60
>down_trylock+0x13/0x70
>__down_trylock_console_sem+0x38/0xc0
>console_trylock+0x17/0xb0
>
Hi all,
While fuzzing with syzkaller inside Qemu I've stumbled on the
following warning which is reproducible with
==
// autogenerated by syzkaller (http://github.com/google/syzkaller)
#define _GNU_SOURCE
#include
#include
#include
Hi all,
While fuzzing with syzkaller inside Qemu I've stumbled on the
following warning which is reproducible with
==
// autogenerated by syzkaller (http://github.com/google/syzkaller)
#define _GNU_SOURCE
#include
#include
#include
8 matches
Mail list logo
