From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, yosryahmed@google.com,
rostedt@goodmis.org, pmladek@suse.com, senozhatsky@chromium.org
Subject: Re: [merged] seq_buf-add-seq_buf_do_printk-helper.patch removed from -mm tree
Date: Fri, 5 May 2023 23:57:54 +0000 [thread overview]
Message-ID: <20230505235754.121741-1-sj@kernel.org> (raw)
In-Reply-To: <20230505224521.C3D6BC433EF@smtp.kernel.org>
Hi Andrew,
On Fri, 05 May 2023 15:45:21 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> The quilt patch titled
> Subject: seq_buf: add seq_buf_do_printk() helper
> has been removed from the -mm tree. Its filename was
> seq_buf-add-seq_buf_do_printk-helper.patch
>
> This patch was dropped because it was merged into mainline or a subsystem tree
Just for headup. I just found the latest mm-unstable indeed dropped the patch
but a patch[1] depends on it. As a result, build fails as below.
CC mm/memcontrol.o
/mm/memcontrol.c: In function ‘mem_cgroup_print_oom_meminfo’:
/mm/memcontrol.c:1693:2: error: implicit declaration of function ‘seq_buf_do_printk’; did you mean ‘seq_buf_bprintf’? [-Werror=implicit-function-declaration]
1693 | seq_buf_do_printk(&s, KERN_INFO);
| ^~~~~~~~~~~~~~~~~
| seq_buf_bprintf
cc1: some warnings being treated as errors
[1] https://lore.kernel.org/mm-commits/20230502201509.B8711C433D2@smtp.kernel.org/
Thanks,
SJ
>
> ------------------------------------------------------
> From: Sergey Senozhatsky <senozhatsky@chromium.org>
> Subject: seq_buf: add seq_buf_do_printk() helper
> Date: Sat, 15 Apr 2023 19:01:10 +0900
>
> (akpm: temporary addition for
> memcg-use-seq_buf_do_printk-with-mem_cgroup_print_oom_meminfo.patch)
>
> Sometimes we use seq_buf to format a string buffer, which we then pass to
> printk(). However, in certain situations the seq_buf string buffer can
> get too big, exceeding the PRINTKRB_RECORD_MAX bytes limit, and causing
> printk() to truncate the string.
>
> Add a new seq_buf helper. This helper prints the seq_buf string buffer
> line by line, using as a delimiter, rather than passing the whole string
> buffer to printk() at once.
>
> Link: https://lkml.kernel.org/r/20230415100110.1419872-1-senozhatsky@chromium.org
> Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> Cc: Steven Rostedt (Google) <rostedt@goodmis.org>
> Cc: Yosry Ahmed <yosryahmed@google.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
next prev parent reply other threads:[~2023-05-05 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 22:45 [merged] seq_buf-add-seq_buf_do_printk-helper.patch removed from -mm tree Andrew Morton
2023-05-05 23:57 ` SeongJae Park [this message]
2023-05-06 0:00 ` Yosry Ahmed
2023-05-06 0:28 ` SeongJae Park
2023-05-06 0:57 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230505235754.121741-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=yosryahmed@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.