Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230718214540.1.I763efc30c57dcc0284d81f704ef581cded8960c8@changeid>
 <ZLcOcr6N+Ty59rBD@redhat.com>
In-Reply-To: <ZLcOcr6N+Ty59rBD@redhat.com>
From:   Rob Barnes <robbarnes@google.com>
Date:   Tue, 18 Jul 2023 16:18:47 -0600
Message-ID: <CA+Dqm32sTcJoh-8LmtegWdihWGJWQdwCUDhmrLhru866uwQzyQ@mail.gmail.com>
Subject: Re: [PATCH] fs: export emergency_sync
To:     "Bill O'Donnell" <billodo@redhat.com>
Cc:     bleung@chromium.org, linux-fsdevel@vger.kernel.org,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        Christian Brauner <brauner@kernel.org>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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.I361812b405bd07772f66660624188=
339ab158772@changeid

On Tue, Jul 18, 2023 at 4:13=E2=80=AFPM Bill O'Donnell <billodo@redhat.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@google.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
> >
>