[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+ZY6u9qqx6FofECrAZ6TmbcqZ=b4GVwHsxV6hZtNsypgQ@mail.gmail.com>
Date: Mon, 6 Aug 2018 13:58:25 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: syzbot <syzbot+bab151e82a4e973fa325@...kaller.appspotmail.com>,
cgroups@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Vladimir Davydov <vdavydov.dev@...il.com>
Subject: Re: WARNING in try_charge
On Mon, Aug 6, 2018 at 1:32 PM, Michal Hocko <mhocko@...nel.org> wrote:
> On Mon 06-08-18 04:27:02, syzbot wrote:
>> Hello,
>>
>> syzbot has tested the proposed patch and the reproducer did not trigger
>> crash:
>>
>> Reported-and-tested-by:
>> syzbot+bab151e82a4e973fa325@...kaller.appspotmail.com
>>
>> Tested on:
>>
>> commit: 8c8399e0a3fb Add linux-next specific files for 20180806
>> git tree: linux-next
>> kernel config: https://syzkaller.appspot.com/x/.config?x=1b6bc1781e49e93e
>> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>> patch: https://syzkaller.appspot.com/x/patch.diff?x=14fe18e2400000
>>
>> Note: testing is done by a robot and is best-effort only.
>
> OK, so this smells like a problem in the previous group oom changes. Or
> maybe it is not very easy to reproduce?
It's possible to ask syzbot to test on a particular tree/commit too.
Powered by blists - more mailing lists