[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4284e00c-8f6d-7c6a-8d46-fa20b074a4b3@suse.cz>
Date: Fri, 27 Oct 2017 13:27:57 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Michal Hocko <mhocko@...nel.org>,
syzbot
<bot+e7353c7141ff7cbb718e4c888a14fa92de41ebaa@...kaller.appspotmail.com>
Cc: akpm@...ux-foundation.org, dan.j.williams@...el.com,
hannes@...xchg.org, jack@...e.cz, jglisse@...hat.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, shli@...com,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
ying.huang@...el.com
Subject: Re: possible deadlock in lru_add_drain_all
On 10/27/2017 11:34 AM, Michal Hocko wrote:
> On Fri 27-10-17 02:22:40, syzbot wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> a31cc455c512f3f1dd5f79cac8e29a7c8a617af8
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
>> compiler: gcc (GCC) 7.1.1 20170620
>> .config is attached
>> Raw console output is attached.
>
> I do not see such a commit. My linux-next top is next-20171018
It's the next-20170911 tag. Try git fetch --tags, but I'm not sure how
many are archived...
Powered by blists - more mailing lists