From: Benjamin Coddington <bcodding@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Hugh Dickins <hughd@google.com>,
Charles Edward Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Anna Schumaker <anna@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: git regression failures with v6.2-rc NFS client
Date: Sun, 05 Feb 2023 11:11:06 -0500 [thread overview]
Message-ID: <3AD5F198-42A1-49F3-85CA-D245775F87DF@redhat.com> (raw)
In-Reply-To: <8f122cb0304632b391759788fe1f72ea1bab1ba0.camel@kernel.org>
On 5 Feb 2023, at 6:24, Jeff Layton wrote:
> I may be missing something, but would it be possible to move to a more
> stable scheme for readdir cookies for tmpfs?
Yes, totally possible but it was pointed out earlier that's not going to
land in 6.2, so this thread's been focused on trying to reason if
85aa8ddc3818 counts as a regression.
Ben
next prev parent reply other threads:[~2023-02-05 16:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 21:15 git regression failures with v6.2-rc NFS client Chuck Lever III
2023-01-31 22:02 ` Benjamin Coddington
2023-02-01 14:10 ` Benjamin Coddington
2023-02-01 15:53 ` Benjamin Coddington
2023-02-03 14:38 ` Chuck Lever III
2023-02-03 15:13 ` Benjamin Coddington
2023-02-03 15:35 ` Chuck Lever III
2023-02-03 17:14 ` Benjamin Coddington
2023-02-03 18:03 ` Chuck Lever III
2023-02-03 20:01 ` Benjamin Coddington
2023-02-03 20:25 ` Chuck Lever III
2023-02-03 22:26 ` Trond Myklebust
2023-02-03 23:11 ` Chuck Lever III
2023-02-03 23:53 ` Hugh Dickins
2023-02-04 0:07 ` Trond Myklebust
2023-02-04 0:15 ` Hugh Dickins
2023-02-04 0:59 ` Trond Myklebust
2023-02-04 11:07 ` Thorsten Leemhuis
2023-02-04 13:15 ` Benjamin Coddington
2023-02-04 16:52 ` Trond Myklebust
2023-02-04 20:44 ` Benjamin Coddington
2023-02-05 11:24 ` Jeff Layton
2023-02-05 16:11 ` Benjamin Coddington [this message]
2023-02-01 15:11 ` Chuck Lever III
2023-02-03 12:39 ` Linux kernel regression tracking (#adding)
2023-02-21 14:58 ` Linux regression tracking #update (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=3AD5F198-42A1-49F3-85CA-D245775F87DF@redhat.com \
--to=bcodding@redhat.com \
--cc=amir73il@gmail.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hughd@google.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=trondmy@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
/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).