All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olga Kornievskaia <olga.kornievskaia@gmail.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] NFSD fix handling of NFSv4.2 SEEK for data within the last hole
Date: Thu, 1 Apr 2021 09:27:56 -0400	[thread overview]
Message-ID: <CAN-5tyETvKvUq_X7+2E0o=9GjJ628DC=QJW5xKA2-X7UHc_DOw@mail.gmail.com> (raw)
In-Reply-To: <YGUm7/HE3HqVJik2@pick.fieldses.org>

On Wed, Mar 31, 2021 at 9:50 PM J. Bruce Fields <bfields@redhat.com> wrote:
>
> On Wed, Mar 31, 2021 at 03:28:19PM -0400, Olga Kornievskaia wrote:
> > From: Olga Kornievskaia <kolga@netapp.com>
> >
> > According to the RFC 7862, "if the server cannot find a
> > corresponding sa_what, then the status will still be NFS4_OK,
> > but sr_eof would be TRUE". If there is a file that ends with
> > a hole and a SEEK request made for sa_what=SEEK_DATA with
> > an offset in the middle of the last hole, then the server
> > has to return OK and set the eof. Currently the linux server
> > returns ERR_NXIO.
>
> Makes sense, but I think you can use the return value from vfs_llseek
> instead of checking the file size again.  E.g.:
>
>         seek->seek_pos = vfs_llseek(nfs->nf_file, seek->seek_offset, whence);
>         if (seek->seek_pos == -ENXIO)
>                 seek->seek_eof = true;

I don't believe this is correct. (1) ENXIO doesn't imply eof. If the
specified seek_offset was beyond the end of the file the server must
return ERR_NXIO and not OK. and (2) for the same reason I need to
check if the requested type was looking for data but didn't find it
because the offset is in the middle of the hole but still within the
file size (thus the need to check if the seek_offset is within the
file size). But I'm happy to check specifically if the seek_pos was
ENXIO (and not the generic negative error) and then also check if
request was for data and request was within file size.

Also while I'm fixing this and have your attention, Can you tell if
the "else if" condition in the original code makes sense to you. I
didn't touch it but I don't think it's correct. "else if
(seek->seek_pos >= i_size_read(file_inode(nf->nf_file)))" I don't
believe this can ever happen. How can vfs_llseek() ever return a
position that is greater than the size of the file (or actually even
equal to it)?

>         else if (seek->seek_pos < 0)
>                 status = nfserrno(seek->seek_pos);
>
> --b.
>
> >
> > Fixes: 24bab491220fa ("NFSD: Implement SEEK")
> > Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
> > ---
> >  fs/nfsd/nfs4proc.c | 10 +++++++---
> >  1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> > index e13c4c81fb89..2e7ceb9f1d5d 100644
> > --- a/fs/nfsd/nfs4proc.c
> > +++ b/fs/nfsd/nfs4proc.c
> > @@ -1737,9 +1737,13 @@ nfsd4_seek(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
> >        *        should ever file->f_pos.
> >        */
> >       seek->seek_pos = vfs_llseek(nf->nf_file, seek->seek_offset, whence);
> > -     if (seek->seek_pos < 0)
> > -             status = nfserrno(seek->seek_pos);
> > -     else if (seek->seek_pos >= i_size_read(file_inode(nf->nf_file)))
> > +     if (seek->seek_pos < 0) {
> > +             if (whence == SEEK_DATA &&
> > +                 seek->seek_offset < i_size_read(file_inode(nf->nf_file)))
> > +                     seek->seek_eof = true;
> > +             else
> > +                     status = nfserrno(seek->seek_pos);
> > +     } else if (seek->seek_pos >= i_size_read(file_inode(nf->nf_file)))
> >               seek->seek_eof = true;
> >
> >  out:
> > --
> > 2.18.2
> >
>

  reply	other threads:[~2021-04-01 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 19:28 [PATCH 1/1] NFSD fix handling of NFSv4.2 SEEK for data within the last hole Olga Kornievskaia
2021-04-01  1:50 ` J. Bruce Fields
2021-04-01 13:27   ` Olga Kornievskaia [this message]
2021-04-01 21:32     ` Rick Macklem
2021-04-02 21:01       ` J. Bruce Fields
     [not found]         ` <CADaq8jeNrA3TexAM0dBxj7LSoooyRna6wU-VomDKovodYTdqKA@mail.gmail.com>
2021-04-05 14:06           ` [nfsv4] " J. Bruce Fields
2021-04-09 20:24         ` Frank Filz
2021-04-02 14:32     ` J. Bruce Fields
2021-04-09 18:39       ` Olga Kornievskaia
2021-04-11 16:43         ` Chuck Lever III
2021-04-13 15:01           ` J. Bruce Fields
2021-04-13 15:31             ` Olga Kornievskaia
2021-04-13 17:30               ` J. Bruce Fields

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='CAN-5tyETvKvUq_X7+2E0o=9GjJ628DC=QJW5xKA2-X7UHc_DOw@mail.gmail.com' \
    --to=olga.kornievskaia@gmail.com \
    --cc=bfields@redhat.com \
    --cc=chuck.lever@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.