[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZMdhYGKvED9IVP4c@infradead.org>
Date: Mon, 31 Jul 2023 00:23:12 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Christian Brauner <brauner@...nel.org>,
Guenter Roeck <linux@...ck-us.net>,
Bill O'Donnell <billodo@...hat.com>,
Rob Barnes <robbarnes@...gle.com>, bleung@...omium.org,
linux-fsdevel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fs: export emergency_sync
On Wed, Jul 19, 2023 at 01:51:25PM -0700, Dmitry Torokhov wrote:
> I am not sure why you would not want modules to use it - in the case we
> have here we detect a catastrophic failure in a critical system
> component (embedded controller crashed) and would like to have as much
> of the logs saved as possible. It is a module because this kind of EC
> may not be present on every system, but when it is present it is very
> much a core component.
I really don't think this is a kernel poicy in any way. Please do
a userspace upcall and let userspace deal with the policy decision.
Powered by blists - more mailing lists