Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp184540ybi; Thu, 30 May 2019 23:12:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqwHrFlAut3E8Rsoaay8jbojZoUiOiiF/VgQY+DxfIlST9ZeD/kV7NYydJe1f7zAj8o18o03 X-Received: by 2002:a65:56cb:: with SMTP id w11mr7206132pgs.236.1559283133633; Thu, 30 May 2019 23:12:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559283133; cv=none; d=google.com; s=arc-20160816; b=b4Gzdw80QpJhEXv6IqS8XRuz4wm7eiTrWUtL5Yq6YYLpib+tBRo+eW99IYGbi0MQ4B 9cFW5xfMw6AotMYXzIoOMG0aHg+H69eWhVcTveNknedGeiCewj6VQmxSkT3/JFvmBq6H bNAPzKrOL+9Yz1jMV4TthN3aSHf8uk9PnY/YwWTCl5Oruk+wuptCUkrvujUUtAzbr3Qd AYvYMqr3FL08ml3aHmnpP7xM35SR46FwXZVSJTY6DqE42X4PMIllSE7y4tMnjhpF/0OK pD1C/SpzJMKeC8EW5f3i493wKSu2mZ7fcQonXVKLwt0U7pvBOX4xhR3JU9tsKupfjnvu JTSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=mECIkjweKVe9lRfO37XWt/iCFvyVYheVWVZfVUAJkuA=; b=aJGU8Ktba4SX2ZhdEnAM8lUElSwwk/jzFSpgqBg2B4OHd8iJqpE4DLMpWw1HRZMwox x2J55zqt7NfiKQhIei6LVksMwnn7WTb4sd0r4LPrMAlxMnlwg2536mvP3ljUfuqlTAGS 7JJT/iQ55pxLIHhvdWxF5kHNrOG1lyFQ+4CFCpddEnYbfsImtXX0tSE331z5Ze7NggOi QrQl8O+rvlQJRpm6vkXriKIFyKxyMCezowp9I5Z980yiD/BszTZKhMOgUf8KyMxTpLGd EMdYIuhe8JisZCo7HWroeJ6BYTGL/QpDU+Qf60xOwC3N0+tE0wdNVl+2jIPBBsn62m7h Nu2g== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h12si4939071plr.247.2019.05.30.23.11.57; Thu, 30 May 2019 23:12:13 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726688AbfEaGKu (ORCPT + 99 others); Fri, 31 May 2019 02:10:50 -0400 Received: from mx2.suse.de ([195.135.220.15]:57264 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726275AbfEaGKu (ORCPT ); Fri, 31 May 2019 02:10:50 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 44BBFAF8E; Fri, 31 May 2019 06:10:49 +0000 (UTC) Date: Fri, 31 May 2019 08:10:47 +0200 From: Michal Hocko To: "Huang, Ying" Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Mike Kravetz , Andrea Parri , "Paul E . McKenney" , Minchan Kim , Hugh Dickins Subject: Re: [PATCH -mm] mm, swap: Fix bad swap file entry warning Message-ID: <20190531061047.GB6896@dhcp22.suse.cz> References: <20190531024102.21723-1-ying.huang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190531024102.21723-1-ying.huang@intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 31-05-19 10:41:02, Huang, Ying wrote: > From: Huang Ying > > Mike reported the following warning messages > > get_swap_device: Bad swap file entry 1400000000000001 > > This is produced by > > - total_swapcache_pages() > - get_swap_device() > > Where get_swap_device() is used to check whether the swap device is > valid and prevent it from being swapoff if so. But get_swap_device() > may produce warning message as above for some invalid swap devices. > This is fixed via calling swp_swap_info() before get_swap_device() to > filter out the swap devices that may cause warning messages. > > Fixes: 6a946753dbe6 ("mm/swap_state.c: simplify total_swapcache_pages() with get_swap_device()") I suspect this is referring to a mmotm patch right? There doesn't seem to be any sha like this in Linus' tree AFAICS. If that is the case then please note that mmotm patch showing up in linux-next do not have a stable sha1 and therefore you shouldn't reference them in the commit message. Instead please refer to the specific mmotm patch file so that Andrew knows it should be folded in to it. Thanks! -- Michal Hocko SUSE Labs