From: "Mantas Mikulėnas" <grawity@gmail.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Data corruption with 5.10.x client -> 6.5.x server
Date: Wed, 27 Sep 2023 11:45:33 +0300 [thread overview]
Message-ID: <5048a7a0-d2fe-41f3-be3b-4eead930c414@gmail.com> (raw)
In-Reply-To: <2660F09A-5823-4581-8977-4F41153724D6@oracle.com>
On 26/09/2023 16.57, Chuck Lever III wrote:
> I'm wondering if I can get you to bisect the server kernel using
> your v5.10 client to test? good = v6.4, bad = v6.5 should do it.
>> Yeah, I will try to bisect but it'll probably take a day or two.
I'm *nearly* done with bisect (most of the builds with distro config
took over an hour on this aging Xeon), and I'm currently in the middle of:
518f375 [refs/bisect/bad] nfsd: don't provide pre/post-op attrs if
fh_getattr fails
df56b38 NFSD: Remove nfsd_readv()
703d752 [HEAD] NFSD: Hoist rq_vec preparation into nfsd_read() [step two]
507df40 NFSD: Hoist rq_vec preparation into nfsd_read()
ed4a567 [refs/bisect/good-XX] NFSD: Update rq_next_page between COMPOUND
operations
next prev parent reply other threads:[~2023-09-27 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 13:07 Data corruption with 5.10.x client -> 6.5.x server Mantas Mikulėnas
2023-09-24 13:28 ` Chuck Lever III
2023-09-24 14:32 ` Mantas Mikulėnas
2023-09-24 14:44 ` Chuck Lever III
2023-09-24 16:51 ` Mantas Mikulėnas
2023-09-24 18:24 ` Chuck Lever III
2023-09-25 19:22 ` Chuck Lever III
2023-09-26 4:41 ` Mantas Mikulėnas
2023-09-26 13:57 ` Chuck Lever III
2023-09-26 21:52 ` Olga Kornievskaia
2023-09-26 22:55 ` Chuck Lever III
2023-09-27 8:45 ` Mantas Mikulėnas [this message]
2023-09-27 9:41 ` Mantas Mikulėnas
2023-09-27 13:08 ` Chuck Lever III
2023-09-27 13:30 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=5048a7a0-d2fe-41f3-be3b-4eead930c414@gmail.com \
--to=grawity@gmail.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.