linux-kernel - [PATCH 0/1] pstore/ram: Ensure stable pmsg address with per-CPU ftrace buffers

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-next>] [day] [month] [year] [list]

Message-Id: <20221011183630.3113666-1-pso@chromium.org>
Date:   Tue, 11 Oct 2022 11:36:29 -0700
From:   pso@...omium.org
To:     LKML <linux-kernel@...r.kernel.org>,
        Linux-Fsdevel <linux-fsdevel@...r.kernel.org>
Cc:     Kees Cook <keescook@...omium.org>,
        Dmitry Torokhov <dtor@...omium.org>,
        Paramjit Oberoi <pso@...omium.org>,
        Anton Vorontsov <anton@...msg.org>,
        Colin Cross <ccross@...roid.com>,
        Tony Luck <tony.luck@...el.com>
Subject: [PATCH 0/1] pstore/ram: Ensure stable pmsg address with per-CPU ftrace buffers

From: Paramjit Oberoi <pso@...omium.org>


Hi pstore maintainers,

Resending a little patch from May: without this change, the start
address of pmsg varies with the number of CPUs in the system. This is a
problem for tools that want to manipulate pstore outside a VM (we are
doing this for crash reporting).



Paramjit Oberoi (1):
  pstore/ram: Ensure stable pmsg address with per-CPU ftrace buffers

 fs/pstore/ram.c | 2 ++
 1 file changed, 2 insertions(+)

-- 
2.38.0.rc1.362.ged0d419d3c-goog