[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230411224652.576dd18c@gandalf.local.home>
Date: Tue, 11 Apr 2023 22:46:52 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Petr Mladek <pmladek@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Yosry Ahmed <yosryahmed@...gle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2] seq_buf: add seq_buf_do_printk() helper
On Tue, 11 Apr 2023 23:38:52 +0900
Sergey Senozhatsky <senozhatsky@...omium.org> wrote:
> 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 \n as a delimiter,
> rather than passing the whole string buffer to printk()
> at once.
>
> Signed-off-by: Sergey Senozhatsky <senozhatsky@...omium.org>
Looks good to me. Want me to pull this in my tree, or do you have
patches dependent on this?
-- Steve
Powered by blists - more mailing lists