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]
Message-ID: <202111161259.D0972333@keescook>
Date:   Tue, 16 Nov 2021 13:00:07 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>, Tony Luck <tony.luck@...el.com>,
        Anton Vorontsov <anton@...msg.org>,
        linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        kernel@...gutronix.de, Colin Cross <ccross@...roid.com>
Subject: Re: [PATCH] pstore/ftrace: add a kernel parameter to start pstore
 recording

On Tue, Nov 16, 2021 at 12:37:05PM -0500, Steven Rostedt wrote:
> On Tue, 16 Nov 2021 18:28:35 +0100
> Uwe Kleine-König <u.kleine-koenig@...gutronix.de> wrote:
> 
> > > Is this still needed? It's still in my internal patchwork, and I haven't
> > > seen any responses.  
> > 
> > I didn't see any responses either, and unless someone else implemented
> > something similar somewhere else, it's still needed.
> > 
> > The change was actually useful to debug a clk problem, where the machine
> > freezed when a certain driver was loaded.
> 
> Perhaps I should ask this. Would anyone object if I just take this change
> through my tree for the next merge window?

If you can Ack it, I'll take it via the pstore tree; I've got a few
other things that will likely need to go in for the next merge window
too.

-Kees

-- 
Kees Cook

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ