[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+Dqm32sTcJoh-8LmtegWdihWGJWQdwCUDhmrLhru866uwQzyQ@mail.gmail.com>
Date: Tue, 18 Jul 2023 16:18:47 -0600
From: Rob Barnes <robbarnes@...gle.com>
To: "Bill O'Donnell" <billodo@...hat.com>
Cc: bleung@...omium.org, linux-fsdevel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fs: export emergency_sync
My use case is when the EC panics. A hard reset is imminent. In my
testing a regular sync did not always sync all of the logs. See
https://lore.kernel.org/all/20230717232932.1.I361812b405bd07772f66660624188339ab158772@changeid
On Tue, Jul 18, 2023 at 4:13 PM Bill O'Donnell <billodo@...hat.com> wrote:
>
> On Tue, Jul 18, 2023 at 09:45:40PM +0000, Rob Barnes wrote:
> > emergency_sync forces a filesystem sync in emergency situations.
> > Export this function so it can be used by modules.
> >
> > Signed-off-by: Rob Barnes <robbarnes@...gle.com>
>
> Example of an emergency situation?
> Thanks-
> Bill
>
>
> > ---
> >
> > fs/sync.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/fs/sync.c b/fs/sync.c
> > index dc725914e1edb..b313db0ebb5ee 100644
> > --- a/fs/sync.c
> > +++ b/fs/sync.c
> > @@ -142,6 +142,7 @@ void emergency_sync(void)
> > schedule_work(work);
> > }
> > }
> > +EXPORT_SYMBOL(emergency_sync);
> >
> > /*
> > * sync a single super
> > --
> > 2.41.0.255.g8b1d071c50-goog
> >
>
Powered by blists - more mailing lists