linux-hardening - Re: [PATCH 0/1] Put seq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 19 Oct 2023 17:14:39 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Matthew Wilcox (Oracle)" <willy@...radead.org>
Cc: 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>
Subject: Re: [PATCH 0/1] Put seq_buf on a diet

On Thu, 19 Oct 2023 20:45:13 +0100
"Matthew Wilcox (Oracle)" <willy@...radead.org> wrote:

> 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.
> 
> 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             | 13 +++++--------
>  5 files changed, 18 insertions(+), 18 deletions(-)
> 

Thanks Matthew, I'll pull this in and add it to my for-next queue (after
testing)

-- Steve