From: Raghav <raghav.original@gmail.com>
To: Jingbo Xu <jefflexu@linux.alibaba.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] FUSE: support for file_flags and birthtime (FreeBSD use case)
Date: Mon, 23 Mar 2026 12:05:44 +0530 [thread overview]
Message-ID: <CABR4S-v_JgdN00E0kZPb04zanBb3ZMv2KJoHm1tbBi3CHBapSg@mail.gmail.com> (raw)
In-Reply-To: <b79abd77-9cf0-44da-8436-b6e4de0e8712@linux.alibaba.com>
Hi Jingbo,
Thanks, I’ll look into FUSE_STATX.
for file flags (chflags), I don’t see an equivalent in the current
FUSE protocol. Do you think we could extend the protocol to support
file flags?
On Sat, Mar 21, 2026 at 11:30 AM Jingbo Xu <jefflexu@linux.alibaba.com> wrote:
>
>
>
> On 3/20/26 5:06 PM, Raghav wrote:
> > Hi all,
> >
> > I’m a new contributor working on improving fusefs in FreeBSD, and I'm
> > bringing up an issue in FUSEFS.
> >
> > FreeBSD supports file flags modification with chflags(2) and file
> > creation time (st_birthtime) at the VFS level. But, these are not
> > currently supported by the FUSE protocol.
> > As a result, fusefs on FreeBSD cannot expose or preserve these attributes.
> >
> > I think we need to append struct fuse_attr with:
> > uint32_t file_flags;
> > uint64_t birthtime;
> > uint32_t birthtimensec;
> > Handling them in a backward compatible way.
> >
> > Is extending fuse_attr in this way acceptable? If so, I’d be happy to
> > make the changes and follow up with a patch.
> >
>
> FUSE supports statx(2) with FUSE_STATX, which exposes btime.
>
> --
> Thanks,
> Jingbo
>
prev parent reply other threads:[~2026-03-23 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 9:06 [RFC] FUSE: support for file_flags and birthtime (FreeBSD use case) Raghav
2026-03-21 6:00 ` Jingbo Xu
2026-03-23 6:35 ` Raghav [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=CABR4S-v_JgdN00E0kZPb04zanBb3ZMv2KJoHm1tbBi3CHBapSg@mail.gmail.com \
--to=raghav.original@gmail.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.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