From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Yosry Ahmed <yosryahmed@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] seq_buf: add seq_buf_do_printk() helper
Date: Fri, 14 Apr 2023 11:00:55 +0200 [thread overview]
Message-ID: <ZDkWR2lq2MZ4r1aG@alley> (raw)
In-Reply-To: <20230411143852.868524-1-senozhatsky@chromium.org>
On Tue 2023-04-11 23:38:52, Sergey Senozhatsky 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.
>
> --- a/lib/seq_buf.c
> +++ b/lib/seq_buf.c
> @@ -93,6 +93,40 @@ int seq_buf_printf(struct seq_buf *s, const char *fmt, ...)
> }
> EXPORT_SYMBOL_GPL(seq_buf_printf);
>
> +/**
> + * seq_buf_do_printk - printk seq_buf line by line
> + * @s: seq_buf descriptor
> + * @lvl: printk level
> + *
> + * printk()-s a multi-line sequential buffer line by line. The function
> + * makes sure that the buffer in @s is nul terminated and safe to read
> + * as a string.
> + */
> +void seq_buf_do_printk(struct seq_buf *s, const char *lvl)
> +{
> + const char *start, *lf;
> + int len;
> +
> + if (s->size == 0 || s->len == 0)
> + return;
> +
> + seq_buf_terminate(s);
> +
> + start = s->buffer;
> + while ((lf = strchr(start, '\n'))) {
> + len = lf - start + 1;
> + printk("%s%.*s", lvl, len, start);
> + start = ++lf;
> + }
> +
> + /* No trailing LF */
> + if (start < s->buffer + s->len) {
> + len = s->buffer + s->len - start;
> + printk("%s%.*s\n", lvl, len, start);
We know that the string is '\0' terminated, so the last print
might be easier:
if (start < s->buffer + s->len)
printk("%s%s\n", lvl, start);
Anyway, it looks good. With or without this change:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2023-04-14 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 14:38 Sergey Senozhatsky
2023-04-12 2:46 ` Steven Rostedt
2023-04-12 3:07 ` Sergey Senozhatsky
2023-04-12 3:14 ` Yosry Ahmed
2023-04-14 9:00 ` Petr Mladek [this message]
2023-04-15 7:04 ` Sergey Senozhatsky
2023-04-15 7:43 ` Steven Rostedt
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=ZDkWR2lq2MZ4r1aG@alley \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®