[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2abff35f-8b06-ff69-0ab1-82f7ea9bb2bd@suse.cz>
Date: Tue, 31 Oct 2017 15:54:38 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Dmitry Vyukov <dvyukov@...gle.com>,
syzbot
<bot+b8ff4d5c3fa77f2e2f0f9be34e6b2795ffc3c65e@...kaller.appspotmail.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
syzkaller-bugs@...glegroups.com,
kasan-dev <kasan-dev@...glegroups.com>
Subject: Re: possible deadlock in __synchronize_srcu
On 10/31/2017 02:20 PM, Dmitry Vyukov wrote:
> On Tue, Oct 31, 2017 at 3:54 PM, syzbot
> <bot+b8ff4d5c3fa77f2e2f0f9be34e6b2795ffc3c65e@...kaller.appspotmail.com>
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 9506597de2cde02d48c11d5c250250b9143f59f7
That's next-20170824. Why test/report such old next trees now?
Powered by blists - more mailing lists