From: Steven Rostedt <rostedt@goodmis.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-hardening@vger.kernel.org,
Nathan Lynch <nathanl@linux.ibm.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [RFC v1] seq_buf: Add seq_buf_create() to implement DECLARE_SEQ_BUF()
Date: Wed, 28 Oct 2026 21:12:27 -0400 [thread overview]
Message-ID: <20261028211227.2b644f2e@fedora> (raw)
In-Reply-To: <9bda534b33f05b90a4b14d343ac70cbbe1d7bd2e.1793229193.git.alx@kernel.org>
On Thu, 29 Oct 2026 00:19:24 +0100
Alejandro Colomar <alx@kernel.org> wrote:
> This implements DECLARE_SEQ_BUF() in a way that is independent of the
> members of the structure.
>
> This will allow transitioning to a different implementation of seq_buf
> which uses pointers instead of sizes, on which I plan to work soon.
>
> The compiler should be able to optimize this out and produce the same
> code as before.
>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Nathan Lynch <nathanl@linux.ibm.com>
> Cc: Kees Cook <keescook@chromium.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
>
> Hi Steve, Kees,
>
> This is a patch that I could split from the rewrite using pointers, so
> we can apply it earlier to reduce the later diff.
>
> I've built a kernel with 'allmodconfig' to check that it's okay.
>
> The reason I need this patch is that we can't calculate the end pointer
> of the compound literal without passing it to a function. If you want
> me to hold this patch and send it together with the rest of the rewrite,
> I can also do that, but I thought this might be useful by itself.
>
>
> Have a lovely night!
> Alex
>
>
> include/linux/seq_buf.h | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/seq_buf.h b/include/linux/seq_buf.h
> index 9f2839e73f8a..facc5643c049 100644
> --- a/include/linux/seq_buf.h
> +++ b/include/linux/seq_buf.h
> @@ -25,10 +25,7 @@ struct seq_buf {
> };
>
> #define DECLARE_SEQ_BUF(NAME, SIZE) \
> - struct seq_buf NAME = { \
> - .buffer = (char[SIZE]) { 0 }, \
> - .size = SIZE, \
> - }
> + struct seq_buf NAME = seq_buf_create((char[SIZE]){0}, SIZE)
It can't use the DECLARE_* name as that is by default something that
can be used outside of a function:
DECLARE_SEQ_BUF(foo, 1024);
Needs to work. Just because nothing does that now, doesn't mean it will
not happen in the future. From my understanding, all DECLARE_* macros
for other types work this way.
-- Steve
>
> static inline void seq_buf_clear(struct seq_buf *s)
> {
> @@ -45,6 +42,15 @@ seq_buf_init(struct seq_buf *s, char *buf, unsigned int size)
> seq_buf_clear(s);
> }
>
> +static inline struct seq_buf
> +seq_buf_create(char *buf, unsigned int size)
> +{
> + struct seq_buf s;
> +
> + seq_buf_init(&s, buf, size);
> + return s;
> +}
> +
> /*
> * seq_buf have a buffer that might overflow. When this happens
> * len is set to be greater than size.
>
> Range-diff against v0:
> -: ------------ > 1: 9bda534b33f0 seq_buf: Add seq_buf_create() to implement DECLARE_SEQ_BUF()
next prev parent reply other threads:[~2026-10-29 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 23:19 [RFC v1] seq_buf: Add seq_buf_create() to implement DECLARE_SEQ_BUF() Alejandro Colomar
2026-10-29 1:12 ` Steven Rostedt [this message]
2026-10-29 11:33 ` Alejandro Colomar
2026-10-29 13:41 ` Steven Rostedt
2026-10-29 14:15 ` Alejandro Colomar
2026-10-29 14:28 ` Steven Rostedt
2026-10-29 15:03 ` Alejandro Colomar
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=20261028211227.2b644f2e@fedora \
--to=rostedt@goodmis.org \
--cc=alx@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=nathanl@linux.ibm.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