From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751542AbdGYIan (ORCPT <rfc822;w@1wt.eu>);
        Tue, 25 Jul 2017 04:30:43 -0400
Received: from mout.gmx.net ([212.227.15.15]:52678 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751522AbdGYIak (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 25 Jul 2017 04:30:40 -0400
Message-ID: <1500971420.20666.2.camel@gmx.de>
Subject: Re: [zram] ltp inspired explosion  - master
 v4.13-rc1-3-g87b2c3fc6317
From: Mike Galbraith <efault@gmx.de>
To: Minchan Kim <minchan@kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>
Cc: Jerome Marchand <jmarchan@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>, Nitin Gupta <ngupta@vflare.org>
Date: Tue, 25 Jul 2017 10:30:20 +0200
In-Reply-To: <20170725062650.GA12134@bbox>
References: <1500283045.7885.37.camel@gmx.de>
         <1500920221.16574.7.camel@gmx.de> <20170725062650.GA12134@bbox>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:HD6CoVwUn3CG1f+xtGvPvaDgS7sXCdmD5NnPvrQud7Lwi4OUTqA
 HoySFT3npX0QGN9mZJ/Q8YTSJb8JB+mJOkpDJrsezeymCrbL9ESFB5/I1J6pwr83mzaQgOC
 yUqVZTzIwXIxdNS44eky023QrPIHE2JIIAKHgu2pKSUG9tRt03W45BlKs4UlWV027DA53qF
 Lm0yoi75hkYIIPweKnx9w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:TaST/3o4Cfg=:DK3iJojOQB2B1x6YppujqV
 1x8GHP4eY6LzoojDshpwe+X+YlA1Bwy2GSl8twK0rL0BXLK2Rc6UZ0XfA2as1US1IyuyM7fz5
 XKmBatg8yxxEXErqFghxtPPW3zFS0MSXD9x2596kUty5a4OfKuz5U+FyH/RvJ7rpK576BE/n3
 IBfyPrRMyigNmrxl2kHA1Kusw04Iov0xTs9UlzA3gSfiB/zT7+/1ghsASe1pCB950WcD2InXH
 voDfAwgsO1e3lJCpiqQrwLtF7SIddJUd1dWVztgjkkAabGxeTYC7ix8Gc0zXnbv2b4w9kIk4K
 of4zPvp8rnZO4j5qiiPm1ZBliPFGhijsettx1bAm2UIfdrf2VWaIBTTjyVLj5g67hN+pP34WT
 e/EDw/lWhO3/z7FRtBgrDX7XbYDozXBl3J9MQ9bkLTA2mmqcoynysdWqQFc0/H39kilDHcCNC
 OmirtpL+CT9/tku9JUjjiZws2LSvGi3dHIG2YxAkv7arywn+qNlfGUAroGDlJP/4hBK8sVvow
 ZqRY5QHhldG+iP5xa12mlvfX1EB/CPavt1WgOErqnc4/s41x+gr/Qtq1ipQZq+k/OFgdstuOD
 i6bY5R2kl15Q0Bj68rrf7pLEMp7utQMQRSKcYJ3AGhbsLk3QxA8z2r/pQncHOHnRD1FQG6YS/
 xdFPqiY/h3LXd/f3WfVcndD/jAe8m84v70dIyynLSy/yV9wUSxyuNtO8wbUlAbRUuhLJ9kRD9
 iYip+duNfaNQMyqdPkuxxQUV0H3wSMZQdfFoRfvKcXOCI9RD5cs7dt0leL+7g2xxBX4ol2PEb
 4W5Cp0i7e9C+/zx91UrF9LTwtOVM5rWNgMl7HllC8Sa3cD+z9I=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 2017-07-25 at 15:26 +0900, Minchan Kim wrote:
> Hi,
> 
> On Mon, Jul 24, 2017 at 08:17:01PM +0200, Mike Galbraith wrote:
> > Now bisected and verified via revert, the culprit is:
> > 
> > cf8e0fedf078 mm/zsmalloc: simplify zs_max_alloc_size handling
> > 
> > Reproducer: ltp::testcases/bin/zram03.
> > 
> 
> Thanks for the report and bisecting.
> I believe this patch should fix it.

Yup, the vm I bisected with is a happy camper.

	-Mike