to a dedicated
location.
> Console output is meant for more complex cases when a developer needs
> to extract some long tail of custom information.
This "INFO: rcu detected stall in ndisc_alloc_skb" is exactly a case where only
syzbot-program lines can provide some clue. And th
On Sat, Jan 19, 2019 at 2:10 PM Tetsuo Handa
wrote:
>
> On 2019/01/19 21:16, Dmitry Vyukov wrote:
> >> The question for me is, whether sysbot can detect hash collision with
> >> different
> >> syz-program lines before writing the hash value to /dev/kmsg, and retry by
> >> modifying
> >> syz-prog
On 2019/01/19 21:16, Dmitry Vyukov wrote:
>> The question for me is, whether sysbot can detect hash collision with
>> different
>> syz-program lines before writing the hash value to /dev/kmsg, and retry by
>> modifying
>> syz-program lines in order to get a new hash value until collision is
>> a
On Fri, Jan 18, 2019 at 6:20 AM Tetsuo Handa
wrote:
>
> Dmitry Vyukov wrote:
> > On Sun, Jan 6, 2019 at 2:47 PM Tetsuo Handa
> > wrote:
> > >
> > > On 2019/01/06 22:24, Dmitry Vyukov wrote:
> > > >> A report at 2019/01/05 10:08 from "no output from test machine (2)"
> > > >> ( https://syzkaller.a
Dmitry Vyukov wrote:
> On Sun, Jan 6, 2019 at 2:47 PM Tetsuo Handa
> wrote:
> >
> > On 2019/01/06 22:24, Dmitry Vyukov wrote:
> > >> A report at 2019/01/05 10:08 from "no output from test machine (2)"
> > >> ( https://syzkaller.appspot.com/text?tag=CrashLog&x=1700726f40 )
> > >> says that ther
On Sun, Jan 6, 2019 at 2:47 PM Tetsuo Handa
wrote:
>
> On 2019/01/06 22:24, Dmitry Vyukov wrote:
> >> A report at 2019/01/05 10:08 from "no output from test machine (2)"
> >> ( https://syzkaller.appspot.com/text?tag=CrashLog&x=1700726f40 )
> >> says that there are flood of memory allocation fa
On 2019/01/06 22:24, Dmitry Vyukov wrote:
>> A report at 2019/01/05 10:08 from "no output from test machine (2)"
>> ( https://syzkaller.appspot.com/text?tag=CrashLog&x=1700726f40 )
>> says that there are flood of memory allocation failure messages.
>> Since continuous memory allocation failure
On Sat, Jan 5, 2019 at 11:49 AM Tetsuo Handa
wrote:
>
> On 2019/01/03 2:06, Tetsuo Handa wrote:
> > On 2018/12/31 17:24, Dmitry Vyukov wrote:
> Since this involves OOMs and looks like a one-off induced memory
> corruption:
>
> #syz dup: kernel panic: corrupted stack end in wb_
On 2019/01/03 2:06, Tetsuo Handa wrote:
> On 2018/12/31 17:24, Dmitry Vyukov wrote:
Since this involves OOMs and looks like a one-off induced memory
corruption:
#syz dup: kernel panic: corrupted stack end in wb_workfn
>>>
>>> Why?
>>>
>>> RCU stall in this case is likely t
On 2018/12/31 17:24, Dmitry Vyukov wrote:
>>> Since this involves OOMs and looks like a one-off induced memory corruption:
>>>
>>> #syz dup: kernel panic: corrupted stack end in wb_workfn
>>>
>>
>> Why?
>>
>> RCU stall in this case is likely to be latency caused by flooding of
>> printk().
>
> Ju
On Mon, Dec 31, 2018 at 9:17 AM Tetsuo Handa
wrote:
>
> On 2018/12/31 16:49, Dmitry Vyukov wrote:
> > On Mon, Dec 31, 2018 at 8:42 AM syzbot
> > wrote:
> >>
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:ef4ab8447aa2 selftests: bpf: install script with_addr.s
On 2018/12/31 16:49, Dmitry Vyukov wrote:
> On Mon, Dec 31, 2018 at 8:42 AM syzbot
> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:ef4ab8447aa2 selftests: bpf: install script with_addr.sh
>> git tree: bpf-next
>> console output: https://syzkaller.appspo
On Mon, Dec 31, 2018 at 8:42 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:ef4ab8447aa2 selftests: bpf: install script with_addr.sh
> git tree: bpf-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14a28b6e40
> kernel config: htt
Hello,
syzbot found the following crash on:
HEAD commit:ef4ab8447aa2 selftests: bpf: install script with_addr.sh
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14a28b6e40
kernel config: https://syzkaller.appspot.com/x/.config?x=7e7e2279c0020d5f
dashbo
14 matches
Mail list logo
