[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231020033545.2587554-1-willy@infradead.org>
Date: Fri, 20 Oct 2023 04:35:44 +0100
From: "Matthew Wilcox (Oracle)" <willy@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "Matthew Wilcox (Oracle)" <willy@...radead.org>,
Kees Cook <keescook@...omium.org>,
Christoph Hellwig <hch@....de>,
Justin Stitt <justinstitt@...gle.com>,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
Kent Overstreet <kent.overstreet@...ux.dev>,
Petr Mladek <pmladek@...e.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
linux-trace-kernel@...r.kernel.org
Subject: [PATCH v2 0/1] Put seq_buf on a diet
Prompted by the recent mails on ksummit, let's actually try to make this
work this time. We need a container for manipulating strings easily,
and seq_buf is the closest thing we have to it. The only problem I have
with it is the readpos that is only useful for the tracing code today.
So move it from the seq_buf to the tracing code.
We should go further with this patch series, including using seq_buf
within vsprintf, but if we can't get over this hurdle first, I'm not
going to waste my time on this again.
v2:
- Add linux-trace-kernel@...r.kernel.org
- Fix kernel-doc
Matthew Wilcox (Oracle) (1):
trace: Move readpos from seq_buf to trace_seq
include/linux/seq_buf.h | 5 +----
include/linux/trace_seq.h | 2 ++
kernel/trace/trace.c | 10 +++++-----
kernel/trace/trace_seq.c | 6 +++++-
lib/seq_buf.c | 22 ++++++++++------------
5 files changed, 23 insertions(+), 22 deletions(-)
--
2.40.1
Powered by blists - more mailing lists