From: Trond Myklebust <trondmy@hammerspace.com>
To: "anna@kernel.org" <anna@kernel.org>,
Lance Shelton <Lance.Shelton@hammerspace.com>,
"jlayton@kernel.org" <jlayton@kernel.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfs: fix bitmap decoder to handle a 3rd word
Date: Wed, 21 Aug 2024 15:37:39 +0000 [thread overview]
Message-ID: <0935dab532078c17847f7d6e26ec76074a39a2ca.camel@hammerspace.com> (raw)
In-Reply-To: <c1d69b024d2a60d2a10e4211c2cbe565ca0e23fb.camel@kernel.org>
On Wed, 2024-08-21 at 11:01 -0400, Jeff Layton wrote:
> On Wed, 2024-08-21 at 14:58 +0000, Trond Myklebust wrote:
> > On Wed, 2024-08-21 at 08:16 -0400, Jeff Layton wrote:
> > > It only decodes the first two words at this point. Have it decode
> > > the
> > > third word as well. Without this, the client doesn't send
> > > delegated
> > > timestamps in the CB_GETATTR response.
> > >
> > > Fixes: 43df7110f4a9 ("NFSv4: Add CB_GETATTR support for delegated
> > > attributes")
> > > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > > ---
> > > Found this while working on the delstid patches for nfsd.
> > > ---
> > > fs/nfs/callback_xdr.c | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/fs/nfs/callback_xdr.c b/fs/nfs/callback_xdr.c
> > > index 29c49a7e5fe1..246470306172 100644
> > > --- a/fs/nfs/callback_xdr.c
> > > +++ b/fs/nfs/callback_xdr.c
> > > @@ -118,7 +118,9 @@ static __be32 decode_bitmap(struct xdr_stream
> > > *xdr, uint32_t *bitmap)
> > > if (likely(attrlen > 0))
> > > bitmap[0] = ntohl(*p++);
> > > if (attrlen > 1)
> > > - bitmap[1] = ntohl(*p);
> > > + bitmap[1] = ntohl(*p++);
> > > + if (attrlen > 2)
> > > + bitmap[2] = ntohl(*p);
> > > return 0;
> > > }
> > >
> > >
> > > ---
> > > base-commit: b311c1b497e51a628aa89e7cb954481e5f9dced2
> > > change-id: 20240821-nfs-6-11-188bb4e1f1dd
> > >
> > > Best regards,
> >
> > Why do we need this? I'm not really understanding which callback
> > attributes we'd want to return in that range.
> >
>
> (note that there is a v2 that fixes a potential buffer overrun with
> this change. We'll want that one)
>
> FATTR4_WORD2_TIME_DELEG_ACCESS and FATTR4_WORD2_TIME_DELEG_MODIFY.
> 43df7110f4a90 added support for those, but the client doesn't see the
> server's request for them without this change.
>
D'oh! Acked...
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2024-08-21 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 12:16 Jeff Layton
2024-08-21 14:58 ` Trond Myklebust
2024-08-21 15:01 ` Jeff Layton
2024-08-21 15:37 ` Trond Myklebust [this message]
2024-08-21 15:53 ` Trond Myklebust
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=0935dab532078c17847f7d6e26ec76074a39a2ca.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=Lance.Shelton@hammerspace.com \
--cc=anna@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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
all inboxes | Powered by JetHome®