From: Kent Overstreet <kent.overstreet@linux.dev>
To: torvalds@linux-foundation.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: [PATCH 2/3] bcachefs: Initialize super_block->s_uuid
Date: Thu, 14 Mar 2024 23:53:01 -0400 [thread overview]
Message-ID: <20240315035308.3563511-3-kent.overstreet@linux.dev> (raw)
In-Reply-To: <20240315035308.3563511-1-kent.overstreet@linux.dev>
Need to fix this oversight for the new UUID/sysfspath ioctls; also,
initialize the sysfs path.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
---
fs/bcachefs/fs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/bcachefs/fs.c b/fs/bcachefs/fs.c
index ec9cf4b8faf1..cfc9d90ab179 100644
--- a/fs/bcachefs/fs.c
+++ b/fs/bcachefs/fs.c
@@ -1881,6 +1881,9 @@ static struct dentry *bch2_mount(struct file_system_type *fs_type,
c->vfs_sb = sb;
strscpy(sb->s_id, c->name, sizeof(sb->s_id));
+ super_set_uuid(sb, c->sb.user_uuid.b, 16);
+ super_set_sysfs_name_uuid(sb);
+
ret = super_setup_bdi(sb);
if (ret)
goto err_put_super;
--
2.43.0
next prev parent reply other threads:[~2024-03-15 3:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 3:52 [PATCH 0/3] bit more FS_IOC_GETFSUUID, FS_IOC_GETFSSYSFSPATH Kent Overstreet
2024-03-15 3:53 ` [PATCH 1/3] bcachefs: Switch to uuid_to_fsid() Kent Overstreet
2024-03-15 3:53 ` Kent Overstreet [this message]
2024-03-15 3:53 ` [PATCH 3/3] ext4: Add support for FS_IOC_GETFSSYSFSPATH Kent Overstreet
2024-03-15 16:45 ` Theodore Ts'o
2024-03-15 16:50 ` Kent Overstreet
2024-03-18 21:51 ` Kiselev, Oleg
2024-03-18 22:22 ` Dave Chinner
2024-03-20 1:49 ` Darrick J. Wong
2024-03-22 23:03 ` Andreas Dilger
2024-05-02 20:00 ` [PATCH 0/3] bit more FS_IOC_GETFSUUID, FS_IOC_GETFSSYSFSPATH Theodore Ts'o
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=20240315035308.3563511-3-kent.overstreet@linux.dev \
--to=kent.overstreet@linux.dev \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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