[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180806113212.GK19540@dhcp22.suse.cz>
Date: Mon, 6 Aug 2018 13:32:12 +0200
From: Michal Hocko <mhocko@...nel.org>
To: syzbot <syzbot+bab151e82a4e973fa325@...kaller.appspotmail.com>
Cc: cgroups@...r.kernel.org, dvyukov@...gle.com, hannes@...xchg.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
penguin-kernel@...ove.SAKURA.ne.jp,
syzkaller-bugs@...glegroups.com, vdavydov.dev@...il.com
Subject: Re: WARNING in try_charge
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?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists