[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+YFX3jiGtugGmO+_taxJgfn9eo1YOz_jufeBmkv_V72uA@mail.gmail.com>
Date: Tue, 26 Jun 2018 16:48:13 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Cc: David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>, rds-devel@....oracle.com,
Santosh Shilimkar <santosh.shilimkar@...cle.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: [PATCH net-next] rds: clean up loopback rds_connections on netns deletion
On Tue, Jun 26, 2018 at 4:44 PM, Sowmini Varadhan
<sowmini.varadhan@...cle.com> wrote:
> On (06/26/18 23:29), David Miller wrote:
>>
>> I think there is a way to ask syzbot to test a patch in an
>> email.
>
> Dmitry/syzkaller-bugs, can you clarify?
>
> This is for the cluster of dup reports like
> https://groups.google.com/forum/#!topic/syzkaller-bugs/zBph8Vu-q2U
> and (most recently)
> https://www.spinics.net/lists/linux-rdma/msg66020.html
>
> as I understand it, if there is no reproducer, you cannot really
> have a pass/fail test to confirm the fix.
This bug has a reproducer as far as I see:
https://syzkaller.appspot.com/bug?id=f4ef381349e100280193c25f24e01d9d364132d9
It seems to be a subtle race since syzbot did not progress with
minimization too much:
https://syzkaller.appspot.com/text?tag=ReproSyz&x=16cbfeaf800000
it probably hit the race by a pure luck of the large program, but then
never had the same luck when tried to remove any syscalls.
So it can make sense to submit several test requests to get more testing.
Powered by blists - more mailing lists