On Fri, Mar 30, 2018 at 12:01 AM, syzbot
wrote:
> Hello,
>
> syzbot hit the following crash on bpf-next commit
> 22527437e0a0c96ee3153e9d0382942b0fd4f9dd (Thu Mar 29 02:36:15 2018 +)
> Merge branch 'nfp-bpf-updates'
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=c7b0dde061c
Hello,
syzbot hit the following crash on bpf-next commit
22527437e0a0c96ee3153e9d0382942b0fd4f9dd (Thu Mar 29 02:36:15 2018 +)
Merge branch 'nfp-bpf-updates'
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=c7b0dde061c523bc4b0f
C reproducer: https://syzkaller.appspot.com/x/r
On Fri, Oct 27, 2017 at 11:36 AM, Eric Dumazet wrote:
> On Fri, 2017-10-27 at 08:09 +0200, Dmitry Vyukov wrote:
>
>> Yes, I've noticed this one. It seems to happen on a first incoming
>> network connection (ssh/scp). I have not seen it before.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/ti
On Fri, 2017-10-27 at 08:09 +0200, Dmitry Vyukov wrote:
> Yes, I've noticed this one. It seems to happen on a first incoming
> network connection (ssh/scp). I have not seen it before.
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=timers/core&id=52f737c2da40259ac9962170ce60
On Thu, Oct 26, 2017 at 6:56 PM, Xin Long wrote:
> Hi all,
>
> I am failed to reproduce it on target kernel with the reproducer file
> or replaying the target syzkaller description log file, do I made
> something wrong or there exists more subjects then the line in
> repro.
On Fri, Oct 27, 2017 at 4:30 AM, ChunYu Wang wrote:
> Maybe I have just made some mistakes on understanding the reproduction
> methods, will try it again.
This is reproducible with the C program. If bot posts it, it was able
to reproduce the bug with the compiled C program. If it was not able
to
Maybe I have just made some mistakes on understanding the reproduction
methods, will try it again.
Thanks,
- ChunYu
On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
> On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
>> Hi all,
>>
>> I am failed to reproduce it on target kernel with th
On Fri, Oct 27, 2017 at 12:56 AM, Xin Long wrote:
> On Fri, Oct 27, 2017 at 12:13 AM, Dmitry Vyukov wrote:
>> On Thu, Oct 26, 2017 at 5:49 PM, Xin Long wrote:
>>> On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
> Hi all,
On Fri, Oct 27, 2017 at 12:13 AM, Dmitry Vyukov wrote:
> On Thu, Oct 26, 2017 at 5:49 PM, Xin Long wrote:
>> On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
>>> On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
Hi all,
I am failed to reproduce it on target kernel with t
On Thu, Oct 26, 2017 at 5:49 PM, Xin Long wrote:
> On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
>> On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
>>> Hi all,
>>>
>>> I am failed to reproduce it on target kernel with the reproducer file
>>> or replaying the target syzkaller descri
On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
> On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
>> Hi all,
>>
>> I am failed to reproduce it on target kernel with the reproducer file
>> or replaying the target syzkaller description log file, do I made
>> something wrong or there exi
On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
> Hi all,
>
> I am failed to reproduce it on target kernel with the reproducer file
> or replaying the target syzkaller description log file, do I made
> something wrong or there exists more subjects then the line in
> repro.txt:
>
> #{Threaded:
Hi all,
I am failed to reproduce it on target kernel with the reproducer file
or replaying the target syzkaller description log file, do I made
something wrong or there exists more subjects then the line in
repro.txt:
#{Threaded:true Collide:true Repeat:false Procs:1 Sandbox:namespace
Fault:false
13 matches
Mail list logo