From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: schumaker anna <schumaker.anna@gmail.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
Anna Schumaker <Anna.Schumaker@Netapp.com>
Subject: Re: [PATCH 0/3] NFS: Disable READ_PLUS by default
Date: Fri, 4 Dec 2020 16:47:40 +0100 (CET) [thread overview]
Message-ID: <852166252.2305208.1607096860375.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <20201203201841.103294-1-Anna.Schumaker@Netapp.com>
Hi Anna,
I see problems with gedeviceinfo and bisected it to c567552612ece787b178e3b147b5854ad422a836.
The commit itself doesn't look that can break it, but might
be can help you find the problem.
What I see, that after xdr_read_pages call the xdr stream points
to a some random point (or wrong page)
Regards,
Tigran.
----- Original Message -----
> From: "schumaker anna" <schumaker.anna@gmail.com>
> To: "linux-nfs" <linux-nfs@vger.kernel.org>
> Cc: "Anna Schumaker" <Anna.Schumaker@Netapp.com>
> Sent: Thursday, 3 December, 2020 21:18:38
> Subject: [PATCH 0/3] NFS: Disable READ_PLUS by default
> From: Anna Schumaker <Anna.Schumaker@Netapp.com>
>
> I've been scratching my head about what's going on with xfstests generic/091
> and generic/263, but I'm not sure what else to look at at this point.
> This patchset disables READ_PLUS by default by marking it as a
> developer-only kconfig option.
>
> I also included a couple of patches fixing some other issues that were
> noticed while inspecting the code. These patches don't help the tests
> pass, but they do fail later on after applying so it does feel like
> progress.
>
> I'm hopeful the remaning issues can be worked out in the future.
>
> Thanks,
> Anna
>
>
> Anna Schumaker (3):
> NFS: Disable READ_PLUS by default
> NFS: Allocate a scratch page for READ_PLUS
> SUNRPC: Keep buf->len in sync with xdr->nwords when expanding holes
>
> fs/nfs/Kconfig | 9 +++++++++
> fs/nfs/nfs42xdr.c | 2 ++
> fs/nfs/nfs4proc.c | 2 +-
> fs/nfs/read.c | 13 +++++++++++--
> include/linux/nfs_xdr.h | 1 +
> net/sunrpc/xdr.c | 3 ++-
> 6 files changed, 26 insertions(+), 4 deletions(-)
>
> --
> 2.29.2
next prev parent reply other threads:[~2020-12-04 15:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:18 [PATCH 0/3] NFS: Disable READ_PLUS by default schumaker.anna
2020-12-03 20:18 ` [PATCH 1/3] " schumaker.anna
2020-12-03 20:18 ` [PATCH 2/3] NFS: Allocate a scratch page for READ_PLUS schumaker.anna
2020-12-03 20:27 ` Chuck Lever
2020-12-03 20:31 ` Anna Schumaker
2020-12-03 20:39 ` Trond Myklebust
2020-12-04 16:14 ` Chuck Lever
2020-12-03 20:18 ` [PATCH 3/3] SUNRPC: Keep buf->len in sync with xdr->nwords when expanding holes schumaker.anna
2020-12-04 15:47 ` Mkrtchyan, Tigran [this message]
2020-12-04 20:00 ` [PATCH 0/3] NFS: Disable READ_PLUS by default Olga Kornievskaia
2020-12-04 22:50 ` Mkrtchyan, Tigran
2020-12-07 15:26 ` Mkrtchyan, Tigran
2020-12-07 15:54 ` Mkrtchyan, Tigran
2020-12-08 12:39 ` Mkrtchyan, Tigran
2020-12-08 13:38 ` Anna Schumaker
2020-12-09 18:23 ` Mkrtchyan, Tigran
2020-12-09 16:59 ` Trond Myklebust
2020-12-09 17:07 ` Olga Kornievskaia
2020-12-09 17:12 ` Trond Myklebust
2020-12-09 17:22 ` Olga Kornievskaia
2020-12-09 17:28 ` Anna Schumaker
2020-12-09 17:39 ` Olga Kornievskaia
2020-12-09 17:32 ` Trond Myklebust
2020-12-09 17:40 ` Olga Kornievskaia
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=852166252.2305208.1607096860375.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=Anna.Schumaker@Netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).