From: Andreas Gruenbacher <agruenba@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org,
Bob Peterson <rpeterso@redhat.com>,
gfs2@lists.linux.dev
Subject: Re: [PATCH] gfs2: fs: derive f_fsid from s_uuid
Date: Tue, 24 Oct 2023 13:15:14 +0200 [thread overview]
Message-ID: <CAHc6FU700V+54hU+JPFYNDLkqicG=UPjU81N3UGmgiTSYnz3-g@mail.gmail.com> (raw)
In-Reply-To: <20231024075535.2994553-1-amir73il@gmail.com>
Amir,
On Tue, Oct 24, 2023 at 9:56 AM Amir Goldstein <amir73il@gmail.com> wrote:
> gfs2 already has optional persistent uuid.
>
> Use that uuid to report f_fsid in statfs(2), same as ext2/ext4/zonefs.
I've applied this patch, thank you.
Andreas
prev parent reply other threads:[~2023-10-24 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 7:55 [PATCH] gfs2: fs: derive f_fsid from s_uuid Amir Goldstein
2023-10-24 9:42 ` Jan Kara
2023-10-24 11:15 ` Andreas Gruenbacher [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHc6FU700V+54hU+JPFYNDLkqicG=UPjU81N3UGmgiTSYnz3-g@mail.gmail.com' \
--to=agruenba@redhat.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rpeterso@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).