[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166576925933.1456464.14312248515298828648.b4-ty@chromium.org>
Date: Fri, 14 Oct 2022 10:41:06 -0700
From: Kees Cook <keescook@...omium.org>
To: gpiccoli@...lia.com, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Kees Cook <keescook@...omium.org>, ardb@...nel.org,
linux-efi@...r.kernel.org, anton@...msg.org,
linux-fsdevel@...r.kernel.org, Tony Luck <tony.luck@...el.com>,
ccross@...roid.com, kernel-dev@...lia.com, kernel@...ccoli.net
Subject: Re: (subset) [PATCH V2 1/3] pstore: Alert on backend write error
On Thu, 13 Oct 2022 18:06:46 -0300, Guilherme G. Piccoli wrote:
> The pstore dump function doesn't alert at all on errors - despite
> pstore is usually a last resource and if it fails users won't be
> able to read the kernel log, this is not the case for server users
> with serial access, for example.
>
> So, let's at least attempt to inform such advanced users on the first
> backend writing error detected during the kmsg dump - this is also
> very useful for pstore debugging purposes.
>
> [...]
Applied to for-next/pstore, thanks!
[1/3] pstore: Alert on backend write error
https://git.kernel.org/kees/c/f181c1af1385
--
Kees Cook
Powered by blists - more mailing lists