Received: by 10.223.176.5 with SMTP id f5csp1995455wra; Sun, 4 Feb 2018 17:44:44 -0800 (PST) X-Google-Smtp-Source: AH8x224k+sHn6+gH2w48BzE9JKnuhdFfl/M3bDVmYD5QXvq8lzHbVBPH964cDxEuMKca0letUFDj X-Received: by 10.98.33.82 with SMTP id h79mr46574726pfh.139.1517795084289; Sun, 04 Feb 2018 17:44:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517795084; cv=none; d=google.com; s=arc-20160816; b=v8oqW2T4FEIISMooxkT/DyRccXrPEhQ2iaHzFVqWPlYH26pAVTA/Qx3okUBQ0Dums2 fvbYyYUXgkdF6/MflI0Oqm/jXk1khI7OCOUxNPX7hEk3Zqfvosc8Llyjl6WGRyoKraLP xc5DLn1fwJOgtE7EjMWiirXz6yqN/UrOvBeHO/BCgycQ1q/mzah4zrjz/VIQxB9OUSP1 nwwEv5d3LEK3Yu9MuPw0SLwv75AN7m9hAzhvyioJDTE31dj2AOUphUKKuSE4h/DpfjaC M02KYdw8a/EPNm/VenTr8olo0W3EjdYAkiTCTQ/S6DX2f85eELkI8k499iogVqkkyNpi 0zjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from :arc-authentication-results; bh=4UEK7M7opTuStvjmgY9wq0R4/L6BHO9xMUiY/IXKWLc=; b=ssFxPDNIGJqn2NiFpKnXhh033f9J3Z+9jzboszjF0Sssd4Ukge1Fgw7DcEChB3I4VJ Ejg73BZct40f5IuARVI1NgrqTHjf+7y895/5eQSniWxfZRqOb/7xAVyky1Hq7Npvo/V0 OlZh8g9J2nFEVLKSYPGIse5//5lz7h6NnAKjWE7kwjQeKVfr1sZAmYXzx7WT5SdRVjWW YjYKO8CTuqnrlYgDcCxMEFkjJ1grroJ0Hik2ILf4/wplUBxta0qknW6qWDSWHwqd60nv 6VMozHnLV3ubmOASc9liN1wyV0vivCFAhttC7l3nTbK3bTBd0LdshqpooyN/1ibsDnpD cZ7g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u18-v6si2759734plq.228.2018.02.04.17.44.30; Sun, 04 Feb 2018 17:44:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752754AbeBEBnh (ORCPT + 99 others); Sun, 4 Feb 2018 20:43:37 -0500 Received: from mga04.intel.com ([192.55.52.120]:62675 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752648AbeBEBm1 (ORCPT ); Sun, 4 Feb 2018 20:42:27 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Feb 2018 17:42:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,462,1511856000"; d="scan'208";a="15834004" Received: from yhuang-dev.sh.intel.com (HELO yhuang-dev) ([10.239.13.10]) by orsmga006.jf.intel.com with ESMTP; 04 Feb 2018 17:42:24 -0800 From: "Huang\, Ying" To: Sergey Senozhatsky Cc: huang ying , Andrew Morton , "Michal Hocko" , Vlastimil Babka , "Sergey Senozhatsky" , Minchan Kim , Seth Jennings , Dan Streetman , "Kirill A . Shutemov" , , LKML Subject: Re: bisected bd4c82c22c367e is the first bad commit (was [Bug 198617] New: zswap causing random applications to crash) References: <20180130114841.aa2d3bd99526c03c6a5b5810@linux-foundation.org> <20180203013455.GA739@jagdpanzerIV> <20180205013758.GA648@jagdpanzerIV> Date: Mon, 05 Feb 2018 09:42:23 +0800 In-Reply-To: <20180205013758.GA648@jagdpanzerIV> (Sergey Senozhatsky's message of "Mon, 5 Feb 2018 10:37:58 +0900") Message-ID: <87shag43gg.fsf@yhuang-dev.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sergey Senozhatsky writes: > Hi, > > On (02/04/18 22:21), huang ying wrote: > [..] >> >> After disabling zswap no crashes at all. >> >> >> >> /etc/systemd/swap.conf >> >> zswap_enabled=1 >> >> zswap_compressor=lz4 # lzo lz4 >> >> zswap_max_pool_percent=25 # 1-99 >> >> zswap_zpool=zbud # zbud z3fold >> > > [..] >> Can you give me some detailed steps to reproduce this? Like the >> kernel configuration file, swap configuration, etc. Any kernel >> WARNING during testing? Can you reproduce this with a real swap >> device instead of zswap? > > No warnings (at least no warnings with my .config). Tested it only with > zram based swap (I'm running swap-less x86 systems, so zram is the easiest > way). It seems it's THP + frontswap that makes things unstable, rather > than THP + swap. > > Kernel zswap boot params: > zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=10 zswap.zpool=zbud > > Then I add a 4G zram swap and run a silly memory hogger. I don't think > you'll have any problems reproducing it, but just in case I attached my > .config Thanks for your information! I will try to reproduce it today! Best Regards, Huang, Ying > -ss