From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@kernel.org>,
syzbot
<bot+e7353c7141ff7cbb718e4c888a14fa92de41ebaa@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
hannes@cmpxchg.org, jack@suse.cz, jglisse@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, shli@fb.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
ying.huang@intel.com
Subject: Re: possible deadlock in lru_add_drain_all
Date: Fri, 27 Oct 2017 13:27:57 +0200 [thread overview]
Message-ID: <4284e00c-8f6d-7c6a-8d46-fa20b074a4b3@suse.cz> (raw)
In-Reply-To: <20171027093418.om5e566srz2ztsrk@dhcp22.suse.cz>
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...
prev parent reply other threads:[~2017-10-27 11:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <089e0825eec8955c1f055c83d476@google.com>
2017-10-27 9:34 ` possible deadlock in lru_add_drain_all Michal Hocko
2017-10-27 9:44 ` Dmitry Vyukov
2017-10-27 9:47 ` Dmitry Vyukov
2017-10-27 13:42 ` Michal Hocko
2017-10-30 8:22 ` Michal Hocko
2017-10-30 10:09 ` Byungchul Park
2017-10-30 15:10 ` Peter Zijlstra
2017-10-30 15:22 ` Peter Zijlstra
2017-10-31 13:13 ` Michal Hocko
2017-10-31 13:51 ` Peter Zijlstra
2017-10-31 13:55 ` Dmitry Vyukov
2017-10-31 14:52 ` Peter Zijlstra
2017-10-31 14:58 ` Michal Hocko
2017-10-31 15:10 ` Peter Zijlstra
2017-11-01 8:59 ` Byungchul Park
2017-11-01 12:01 ` Peter Zijlstra
2017-11-01 23:54 ` Byungchul Park
2018-02-14 14:01 ` Dmitry Vyukov
2018-02-14 15:44 ` Michal Hocko
2018-02-14 15:57 ` Dmitry Vyukov
2017-10-31 15:25 ` Peter Zijlstra
2017-10-31 15:45 ` Michal Hocko
2017-10-31 16:30 ` Peter Zijlstra
2017-11-01 8:31 ` Byungchul Park
2017-10-30 10:26 ` Byungchul Park
2017-10-30 11:48 ` Michal Hocko
2017-10-27 11:27 ` Vlastimil Babka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4284e00c-8f6d-7c6a-8d46-fa20b074a4b3@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bot+e7353c7141ff7cbb718e4c888a14fa92de41ebaa@syzkaller.appspotmail.com \
--cc=dan.j.williams@intel.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shli@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).