Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp227484imu; Tue, 27 Nov 2018 11:27:21 -0800 (PST) X-Google-Smtp-Source: AFSGD/X7WWB6TRIeqVFAxGaI0o7PMe75qZN/KW/6NnqP8OiaJixOIQB/f/O4PWVnoL5EyCCDKiFA X-Received: by 2002:a17:902:bb98:: with SMTP id m24mr33002146pls.71.1543346841158; Tue, 27 Nov 2018 11:27:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543346841; cv=none; d=google.com; s=arc-20160816; b=SuTZUZMju15+1rAQgOFy7AiD5SIlaPutWSRrwHBbLxhFCK5YM4TGrR3QRHjDYjWR5y aHkd7vLFuyjoL1BDEsJoAHiVpCEieL1OtZ0FTRUzHNs2IQG+TSkMOps9UzUqRpWXgMxM f7/64vMvmiyK/nCroawRcuKPHg3bEKyem+YbLtvaYtLVRGfYE93eHcjs71ZZNDER0X1G vvWLu1CVxqhW+CmpFEghzx1Iz0VvG/l9UUi07JclCHRH0J4NQdN2XqY9hol2YA6lGvEr CW24gLRAayoFffr0RsN+KvbCRhwzcziMF9qsNtYsa7YubG/TyZ0l4NOcbRNkeep8DWby UiyA== 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=iAT9UXQPe2IsD7QPFHuDlja73nl2Bk8gOk7A2WeCaVU=; b=i6vFbXTxq5zpmskykCnn4LGOf/tF8kfx+/4212/5XhZtzJ6BD2EhrJamOZRC5IPYu3 bcXdzUjDDel3CGZQairO0AafyES7fxx+ehf8LX/hDSk7pQAieTEj0shj24s0nbxMt48H sJZ/J52YP/Smm9/gKJPQz3LPivhGF/KEGGFWavCE0Dij4C++FhdDAeZvhiLMAimabfWU SfyyAsmxQDrFtWqla2Hm9XJ+dlISwE3v1jUFcAo1aXJJJ3zV3vze9pwXHwMPFUgDcU3S TgTnjcpwgHydelWErZi1ileKRQEPSZxqbpbqvMRoAo5MeYuRzIe9ckwO4qFnOCMvq4Ze 46Zw== 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 a10si4549363plp.167.2018.11.27.11.27.06; Tue, 27 Nov 2018 11:27:21 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731040AbeK1D1p (ORCPT + 99 others); Tue, 27 Nov 2018 22:27:45 -0500 Received: from mx2.suse.de ([195.135.220.15]:59276 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726768AbeK1D1p (ORCPT ); Tue, 27 Nov 2018 22:27:45 -0500 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 8BB4AAB6D; Tue, 27 Nov 2018 16:29:17 +0000 (UTC) Date: Tue, 27 Nov 2018 17:29:16 +0100 From: Michal Hocko To: Heiko Carstens Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, linux-mm@kvack.org, "Kirill A . Shutemov" , Martin Schwidefsky Subject: Re: [PATCH] mm: warn only once if page table misaccounting is detected Message-ID: <20181127162916.GB6923@dhcp22.suse.cz> References: <20181127083603.39041-1-heiko.carstens@de.ibm.com> <20181127131916.GX12455@dhcp22.suse.cz> <20181127143638.GE3625@osiris> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181127143638.GE3625@osiris> 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 Tue 27-11-18 15:36:38, Heiko Carstens wrote: > On Tue, Nov 27, 2018 at 02:19:16PM +0100, Michal Hocko wrote: > > On Tue 27-11-18 09:36:03, Heiko Carstens wrote: > > > Use pr_alert_once() instead of pr_alert() if page table misaccounting > > > has been detected. > > > > > > If this happens once it is very likely that there will be numerous > > > other occurrence as well, which would flood dmesg and the console with > > > hardly any added information. Therefore print the warning only once. > > > > Have you actually experience a flood of these messages? Is one per mm > > message really that much? > > Yes, I did. Since in this case all compat processes caused the message > to appear, I saw thousands of these messages. This means something went colossally wrong and seeing an avalanche of messages might be actually helpful because you can at least see the pattern. I wonder whether the underlying issue would be obvious from a single instance. Maybe we want ratelimit instead? > > If yes why rss counters do not exhibit the same problem? > > No rss counter messages appeared. Or do you suggest that the other > pr_alert() within check_mm() should also be changed? Whatever we go with (and I do not have a strong opinion here) we should be consistent I believe. -- Michal Hocko SUSE Labs