Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp27685ybi; Thu, 30 May 2019 19:44:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqzF7/i36lqvutZ53s6dn8KAedvj4y1uZZxgkszsowSOtRRng/14I60gp1ysWqTu3djSjtby X-Received: by 2002:a63:f44b:: with SMTP id p11mr6638339pgk.225.1559270675528; Thu, 30 May 2019 19:44:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559270675; cv=none; d=google.com; s=arc-20160816; b=sfQWIkKtfntqGqK4tSnBEidxhz6YlRJMxpDZ+cPCMDLIPfcjQ0vOue/OYuD+c/SRzz hLOpmkFxC6q+H/RBC8LxxkbI7xIJlwHBU3ca5ltztem19OMLluPxmbKng9bFUqK4o5Gl hSjyTxWdBW1MlkRydUIISCF4AM55SjeNVBGIQdPN8yymynH89SENr7PWFd/VC0vq3sd2 ucfz2ISh2At2V2naut9dQhNwW3QCuiQ/4+aw6CVePPtTL1famOnbQp8XgAsb/aI4pAqH RaUpRMjhxl03IX8yBgmQ8FY5ooa+PMcPCG7kdC86QCqHdW8iRyssltFJfVrZ9Oa8CxDw R+1Q== 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; bh=tU7jex5GIzwZejVuIEKLBEybbkHIktkFUjNVgunM9dM=; b=fr9Tx4rYpDZvBWUvqYOwWdcAy5CzUnSL5+xQ8bfIpLeFDQRChuWneow819jxtFLAOQ v3xIdxSiwqwftAINvqcHB0q927ABmJNlGFB1FONp3s4Bcis4qI0lCGbCZuEZsIxCx08V VUEhesv27pCdxJcLFcIDUb0rT9q+qMZtN23OI5IfdEEOwB1RQNUsP/7V7qXj0VBdn1QS Mq7RHruRmBeXL3hOSa5gwOdsNTsu9INR8GXAoy1/dctlKEfeAyuHDHjGZ3x61rWvzWnR n5GJ8hHbwNfTU0AJL50wno+Se+wtHv5aWkA3Ns6khiCaD9zz94eTkJvxiZYpvXzxLWBh fgTA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w21si965613ply.324.2019.05.30.19.44.19; Thu, 30 May 2019 19:44:35 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726684AbfEaCmi (ORCPT + 99 others); Thu, 30 May 2019 22:42:38 -0400 Received: from mga01.intel.com ([192.55.52.88]:61451 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726512AbfEaCmh (ORCPT ); Thu, 30 May 2019 22:42:37 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 May 2019 19:42:37 -0700 X-ExtLoop1: 1 Received: from yhuang-dev.sh.intel.com (HELO yhuang-dev) ([10.239.159.29]) by fmsmga001.fm.intel.com with ESMTP; 30 May 2019 19:42:35 -0700 From: "Huang\, Ying" To: Mike Kravetz Cc: , , , , , , , , Subject: Re: mmotm 2019-05-29-20-52 uploaded References: <20190530035339.hJr4GziBa%akpm@linux-foundation.org> <87lfyn5rgu.fsf@yhuang-dev.intel.com> Date: Fri, 31 May 2019 10:42:35 +0800 In-Reply-To: <87lfyn5rgu.fsf@yhuang-dev.intel.com> (Ying Huang's message of "Fri, 31 May 2019 09:43:13 +0800") Message-ID: <87h89b5opw.fsf@yhuang-dev.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (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 "Huang, Ying" writes: > Hi, Mike, > > Mike Kravetz writes: > >> On 5/29/19 8:53 PM, akpm@linux-foundation.org wrote: >>> The mm-of-the-moment snapshot 2019-05-29-20-52 has been uploaded to >>> >>> http://www.ozlabs.org/~akpm/mmotm/ >>> >> >> With this kernel, I seem to get many messages such as: >> >> get_swap_device: Bad swap file entry 1400000000000001 >> >> It would seem to be related to commit 3e2c19f9bef7e >>> * mm-swap-fix-race-between-swapoff-and-some-swap-operations.patch > > Hi, Mike, > > Thanks for reporting! I find an issue in my patch and I can reproduce > your problem now. The reason is total_swapcache_pages() will call > get_swap_device() for invalid swap device. So we need to find a way to > silence the warning. I will post a fix ASAP. I have sent out a fix patch in another thread with title "[PATCH -mm] mm, swap: Fix bad swap file entry warning" Can you try it? Best Regards, Huang, Ying