From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 188CBC7EE26 for ; Wed, 3 May 2023 17:52:28 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8A9EB6B007B; Wed, 3 May 2023 13:52:28 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 85A6E6B007D; Wed, 3 May 2023 13:52:28 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 748C86B007E; Wed, 3 May 2023 13:52:28 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-yw1-f201.google.com (mail-yw1-f201.google.com [209.85.128.201]) by kanga.kvack.org (Postfix) with ESMTP id 578926B007B for ; Wed, 3 May 2023 13:52:28 -0400 (EDT) Received: by mail-yw1-f201.google.com with SMTP id 00721157ae682-559de0d40b1so86751927b3.0 for ; Wed, 03 May 2023 10:52:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1683136348; x=1685728348; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=RZYSjSUR1TVNLCONU/ktPYm4b5B8g2ry+YtlqDqVDwA=; b=06jHQvfsD3SDUJMSu6ULA+Lqi2Rheb3urP5pez8MV1dafSxYy0/iecp7i3W9YM8kw0 Z8sDp7LJx6LxY6887Lp9tpfA2PRnZ+5qsmf/2ne9kOhMV6oNSgGhzuXqwMC3i6HQpw8p D8X9p8yhzKfJ/bgSYEC5uIPGefibu0HxTKSIOIWINb3PnNySA5vrkGDdfiFHPxJVa3eg fzeTNSZPX/rk1YdIOuq6L93DdQc6YUPO6bt/7O5Wu9R3mWPc7MGSncLmqdQi7vfNKPNv eNUJWumFkZPqhtINkPq+WqdkN0g7gmfclLzeSV9JpuQEB/g+6NsZV9V3lB08IqjbYy4P Yf/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683136348; x=1685728348; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=RZYSjSUR1TVNLCONU/ktPYm4b5B8g2ry+YtlqDqVDwA=; b=lFJFnnoQDJrl6TXmqS/58ttMhizAVX66gZYOwHjdxuuc400SgwB4hHB17R6qf7vIxU zBiZBLVI/MvQUdwxnlis8EXTDyZ1dNZJwq5j6BoTtOkp7JZcvAAA1K3tj/V2WZ/7klUR 1jOGtHEDtvcBi/HgDreASQx7dn8lvY1+sriLYguoqj9ElMGPsXb9ztm5hwq9QwoZKOBN UL6+GjHjGRv6wq8mHDzX3LB/1Rtnzr/LXedP+WIA9NwKiUSB7eROBB4QA9iOXIv2tRzi bE0I2Basrkd2/03ZLi/T1LG6PahxoKEm8sTIVlO874E6fBxgF0v1nbhhE4f8LkU9ty3e BUlA== X-Gm-Message-State: AC+VfDyHBHB2oupoY4TNn7BeBvfl3Okzn/pWKWosoB10lIHmuDvmgKAz rFoJdO7EEH6MB9IqF5cE+DHvv9KtOcrjNw== X-Google-Smtp-Source: ACHHUZ59iAxehhHtXCF+bq4Cz843yfeiUKwoHIntE4kQjpxt94wcmUOFlOiSBWPXCkx4jhERPUtGCVXYZdfeOw== X-Received: from shakeelb.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:262e]) (user=shakeelb job=sendgmr) by 2002:a81:4054:0:b0:534:d71f:14e6 with SMTP id m20-20020a814054000000b00534d71f14e6mr12118393ywn.9.1683136347929; Wed, 03 May 2023 10:52:27 -0700 (PDT) Date: Wed, 3 May 2023 17:52:26 +0000 In-Reply-To: <20230428132406.2540811-2-yosryahmed@google.com> Mime-Version: 1.0 References: <20230428132406.2540811-1-yosryahmed@google.com> <20230428132406.2540811-2-yosryahmed@google.com> Message-ID: <20230503175226.nyjmmbnohm6xxckd@google.com> Subject: Re: [PATCH v2 1/2] memcg: use seq_buf_do_printk() with mem_cgroup_print_oom_meminfo() From: Shakeel Butt To: Yosry Ahmed Cc: Johannes Weiner , Michal Hocko , Roman Gushchin , Andrew Morton , Muchun Song , Sergey Senozhatsky , Steven Rostedt , Petr Mladek , Chris Li , cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Michal Hocko Content-Type: text/plain; charset="us-ascii" X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Apr 28, 2023 at 01:24:05PM +0000, Yosry Ahmed wrote: > Currently, we format all the memcg stats into a buffer in > mem_cgroup_print_oom_meminfo() and use pr_info() to dump it to the logs. > However, this buffer is large in size. Although it is currently working > as intended, ther is a dependency between the memcg stats buffer and the > printk record size limit. > > If we add more stats in the future and the buffer becomes larger than > the printk record size limit, or if the prink record size limit is > reduced, the logs may be truncated. > > It is safer to use seq_buf_do_printk(), which will automatically break > up the buffer at line breaks and issue small printk() calls. > > Refactor the code to move the seq_buf from memory_stat_format() to its > callers, and use seq_buf_do_printk() to print the seq_buf in > mem_cgroup_print_oom_meminfo(). > > Signed-off-by: Yosry Ahmed > Acked-by: Michal Hocko > Reviewed-by: Sergey Senozhatsky Acked-by: Shakeel Butt