[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZLcOcr6N+Ty59rBD@redhat.com>
Date: Tue, 18 Jul 2023 17:13:06 -0500
From: Bill O'Donnell <billodo@...hat.com>
To: Rob Barnes <robbarnes@...gle.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
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