From: Hongbo Li <lihongbo22@huawei.com>
To: Youling Tang <youling.tang@linux.dev>
Cc: <linux-bcachefs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: Re: [PATCH 2/2] bcachefs: Add support for FS_IOC_GETFSSYSFSPATH
Date: Tue, 9 Jul 2024 10:27:12 +0800 [thread overview]
Message-ID: <5f5c2087-8508-4ed9-8f47-aba0bd73eca6@huawei.com> (raw)
In-Reply-To: <c3471af6-0df7-44a9-8272-ab211f0f1b1b@linux.dev>
On 2024/7/9 10:11, Youling Tang wrote:
> On 09/07/2024 10:04, Hongbo Li wrote:
>>
>>
>> On 2024/7/9 9:11, Youling Tang wrote:
>>> From: Kent Overstreet <kent.overstreet@linux.dev>
>>>
>>> [TEST]:
>>> ```
>>> $ cat ioctl_getsysfspath.c
>>> #include <stdio.h>
>>> #include <stdlib.h>
>>> #include <fcntl.h>
>>> #include <sys/ioctl.h>
>>> #include <linux/fs.h>
>>> #include <unistd.h>
>>>
>>> int main(int argc, char *argv[]) {
>>> int fd;
>>> struct fs_sysfs_path sysfs_path = {};
>>>
>>> if (argc != 2) {
>>> fprintf(stderr, "Usage: %s <path_to_file_or_directory>\n",
>>> argv[0]);
>>> exit(EXIT_FAILURE);
>>> }
>>>
>>> fd = open(argv[1], O_RDONLY);
>>> if (fd == -1) {
>>> perror("open");
>>> exit(EXIT_FAILURE);
>>> }
>>>
>>> if (ioctl(fd, FS_IOC_GETFSSYSFSPATH, &sysfs_path) == -1) {
>>> perror("ioctl FS_IOC_GETFSSYSFSPATH");
>>> close(fd);
>>> exit(EXIT_FAILURE);
>>> }
>>>
>>> printf("FS_IOC_GETFSSYSFSPATH: %s\n", sysfs_path.name);
>>> close(fd);
>>> return 0;
>>> }
>>>
>>> $ gcc ioctl_getsysfspath.c
>>> $ sudo bcachefs format /dev/sda
>>> $ sudo mount.bcachefs /dev/sda /mnt
>>> $ sudo ./a.out /mnt
>>> FS_IOC_GETFSSYSFSPATH: bcachefs/c380b4ab-fbb6-41d2-b805-7a89cae9cadb
>>> ```
>>>
>>> Original patch link:
>>> [1]:
>>> https://lore.kernel.org/all/20240207025624.1019754-8-kent.overstreet@linux.dev/
>>>
>>> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
>>> Signed-off-by: Youling Tang <youling.tang@linux.dev>
>>> ---
>>> fs/bcachefs/fs.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/fs/bcachefs/fs.c b/fs/bcachefs/fs.c
>>> index 011ee5075a52..8699770398d1 100644
>>> --- a/fs/bcachefs/fs.c
>>> +++ b/fs/bcachefs/fs.c
>>> @@ -1978,6 +1978,7 @@ static int bch2_fs_get_tree(struct fs_context *fc)
>>> sb->s_time_min = div_s64(S64_MIN,
>>> c->sb.time_units_per_sec) + 1;
>>> sb->s_time_max = div_s64(S64_MAX,
>>> c->sb.time_units_per_sec);
>>> super_set_uuid(sb, c->sb.user_uuid.b, sizeof(c->sb.user_uuid));
>>> + super_set_sysfs_name_uuid(sb);
>>
>> Reviewed-by: Hongbo Li <lihongbo22@huawei.com>
>>
>> It's quite strange that other commits have been merged, but the ones
>> for bcachefs have not been merged.
> Because bcachefs was not upstream at the time, [1] described the following:
> Note, I dropped the bcachefs changes because they're not upstream yet.
> But once this is a stable branch you can just pull in vfs.uuid and rely
> on that.
>
Got it! Thank you!
Thanks,
Hongbo
> [1]:
> https://lore.kernel.org/all/20240208-wecken-nutzen-3df1102a39b2@brauner/
>
> Thanks,
> Youling.
prev parent reply other threads:[~2024-07-09 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 1:11 [PATCH 1/2] bcachefs: Add support for FS_IOC_GETFSUUID Youling Tang
2024-07-09 1:11 ` [PATCH 2/2] bcachefs: Add support for FS_IOC_GETFSSYSFSPATH Youling Tang
2024-07-09 2:04 ` Hongbo Li
2024-07-09 2:11 ` Youling Tang
2024-07-09 2:27 ` Hongbo Li [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=5f5c2087-8508-4ed9-8f47-aba0bd73eca6@huawei.com \
--to=lihongbo22@huawei.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=youling.tang@linux.dev \
/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
all inboxes | Powered by JetHome®