On Mon, 11 Jul 2022 14:19:41 -0400
Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
> On Mon, Jul 11, 2022 at 06:33:04AM -0400, Jeff Layton wrote:
> > On Sun, 2022-07-10 at 16:42 +0000, Chuck Lever III wrote:
> > > > This patch regressed clients that support TIME_CREATE attribute.
> > > > Starting with this patch client might think that server supports
> > > > TIME_CREATE and start sending this attribute in its requests.
> > >
> > > Indeed, e377a3e698fb ("nfsd: Add support for the birth time
> > > attribute") does not include a change to nfsd4_decode_fattr4()
> > > that decodes the birth time attribute.
> > >
> > > I don't immediately see another storage protocol stack in our
> > > kernel that supports a client setting the birth time, so NFSD
> > > might have to ignore the client-provided value.
> > >
> >
> > Cephfs allows this. My thinking at the time that I implemented it was
> > that it should be settable for backup purposes, but this was possibly a
> > mistake. On most filesystems, the btime seems to be equivalent to inode
> > creation time and is read-only.
>
> So supporting it as read-only seems reasonable.
>
> Clearly, failing to decode the setattr attempt isn't the right way to do
> that. I'm not sure what exactly it should be doing--some kind of
> permission error on any setattr containing TIME_CREATE?
erroring out on TIME_CREATE will break client that try to
set this attribute (legitimately). That's what by chance
happening with current master (return error when TIME_CREATE
is present).
As long as server advertises support for TIME_CREATE
it should not error out when client sends it if spec permits
such use.
I think ignoring this attribute like Chuck has proposed
is acceptable (if one ignores archiving use case where
setting it makes sense).
Alternatively if folks inclined towards erroring out,
there should be a way to optout or optin from TIME_CREATE support,
to keep existing clients working + a sane error message so users
won't have to debug kernel to figure out what's wrong with
their setup.
> --b.
>
