Re: WARNING in port_delete

2019-04-02 Thread Dmitry Vyukov
On Mon, Apr 1, 2019 at 9:25 PM Paul E. McKenney wrote: > > On Mon, Apr 01, 2019 at 12:58:01AM -0700, syzbot wrote: > > syzbot has bisected this bug to: > > > > commit 63d86a7e85f84b8ac3b2f394570965aedbb03787 > > Author: Paul E. McKenney > > Date: Tue May 1 20:08:46 2018 + > > > > rcu: C

Re: WARNING in port_delete

2019-04-01 Thread Paul E. McKenney
On Mon, Apr 01, 2019 at 12:58:01AM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 63d86a7e85f84b8ac3b2f394570965aedbb03787 > Author: Paul E. McKenney > Date: Tue May 1 20:08:46 2018 + > > rcu: Convert rcu_grace_period_init tracepoint to gp_seq > > bisection log: h

Re: WARNING in port_delete

2019-04-01 Thread syzbot
syzbot has bisected this bug to: commit 63d86a7e85f84b8ac3b2f394570965aedbb03787 Author: Paul E. McKenney Date: Tue May 1 20:08:46 2018 + rcu: Convert rcu_grace_period_init tracepoint to gp_seq bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17f86d2f20 start commit:

Re: WARNING in port_delete

2018-10-06 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:091a1eaa0e30 Merge branch 'akpm' git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=16623e5940 kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb dashboard link: h

Re: WARNING in port_delete

2018-07-24 Thread Takashi Iwai
On Tue, 24 Jul 2018 09:14:14 +0200, DaeRyong Jeong wrote: > > I agree with that having a C reproducer would be much better. > Now I'm working on it. > I will immediately let you know once I get the C reproducer. That's great, thanks! Takashi > > > Thank you. > > Best regards, > DaeRyong Jeo

Re: WARNING in port_delete

2018-07-24 Thread DaeRyong Jeong
I agree with that having a C reproducer would be much better. Now I'm working on it. I will immediately let you know once I get the C reproducer. Thank you. Best regards, DaeRyong Jeong On 24 Jul 2018, 4:00 PM +0900, Takashi Iwai , wrote: > On Tue, 24 Jul 2018 05:59:56 +0200, > DaeRyong Jeong wr

Re: WARNING in port_delete

2018-07-24 Thread Takashi Iwai
On Tue, 24 Jul 2018 05:59:56 +0200, DaeRyong Jeong wrote: > > I just realized that the crash has been spotted by Syzkaller a few days > before. > (https://syzkaller.appspot.com/bug?id=3490860a465e6b39227c6906f0ef2d40ad4d5bb1) > > I'm CC'ing Syzkaller's mailing list. It's very likely a false-pos

Re: WARNING in port_delete

2018-07-23 Thread DaeRyong Jeong
te: > Reporting the crash: WARNING in port_delete > > This crash has been found in v4.18-rc3 using RaceFuzzer (a modified > version of Syzkaller), which we descrbie more at the end of this > report. Our analysis shows that the race occurs when invoking two close > syscalls concurr

WARNING in port_delete

2018-07-23 Thread Dae R. Jeong
Reporting the crash: WARNING in port_delete This crash has been found in v4.18-rc3 using RaceFuzzer (a modified version of Syzkaller), which we descrbie more at the end of this report. Our analysis shows that the race occurs when invoking two close syscalls concurrently. The executed program is

WARNING in port_delete

2018-07-11 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:30c2c32d7f70 Merge tag 'drm-fixes-2018-07-10' of git://ano.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=139408c840 kernel config: https://syzkaller.appspot.com/x/.config?x=25856fac4e580aa7 da