From: Eric Van Hensbergen <ericvh@kernel.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
evanhensbergen@icloud.com,
MPTCP Upstream <mptcp@lists.linux.dev>,
v9fs@lists.linux.dev
Subject: Re: 9p: MPTCP tests regressions due to new 9p features in v6.4
Date: Mon, 7 Aug 2023 10:56:48 -0500 [thread overview]
Message-ID: <CAFkjPT=xrkc1UVVFO8Qt35iEUWDTY0MMKO+CxwosySZvpME5vQ@mail.gmail.com> (raw)
In-Reply-To: <bad1180f-dc6d-45d8-9acc-08edd548261a@tessares.net>
That's good news because I was having a horrible time reproducing it.
I'm glad we removed that extra bit, we were thinking it was benign,
but I guess it turns out it wasn't!
-eric
On Mon, Aug 7, 2023 at 10:42 AM Matthieu Baerts
<matthieu.baerts@tessares.net> wrote:
>
> Hi Eric,
>
> On 13/06/2023 18:07, Eric Van Hensbergen wrote:
> > Understood, this on top of my 9p stack, but day job has been getting
> > in the way lately so I need to unstack there first. Will do my best
> > to reproduce and understand as quickly as I can -- but given its a
> > performance regression it is likely going to be tricky to reproduce
> > and understand, so I'm not sure how confident I am that we'll be able
> > to close it out prior to the final -rc.
>
> Good news, it looks like the bug has been fixed!
>
> I recently noticed some new patches fixing some issues in 9p in Linus
> tree because they were conflicting with the revert of 9p's v6.4 PR I did
> in June to stop having random issues in our tests. I then tried
> reproducing the issue we had on top of Linus' tree and I was not able
> too! (but I was still able to reproduce them just before the recent fixes)
>
> After a quick git bisect, it seems the bug is fixed thanks to
> 350cd9b95975 ("fs/9p: remove unnecessary invalidate_inode_pages2").
>
> So we can also tell regzbot to stop tracking this:
>
> #regzbot fix: 350cd9b95975
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
next prev parent reply other threads:[~2023-08-07 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:30 9p: MPTCP tests regressions due to new 9p features in v6.4 Matthieu Baerts
[not found] ` <CAFkjPTnX0=-GK8sFzd4S+V2+cA8E-FAqYHNndZui2Sh_MvoHPw@mail.gmail.com>
2023-06-06 15:08 ` Matthieu Baerts
2023-06-06 18:47 ` evanhensbergen
2023-06-13 14:56 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-13 16:07 ` Eric Van Hensbergen
2023-06-13 16:27 ` Matthieu Baerts
2023-06-22 7:53 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-29 14:29 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-07 15:42 ` Matthieu Baerts
2023-08-07 15:56 ` Eric Van Hensbergen [this message]
2023-06-29 8:46 ` Eric Van Hensbergen
2023-06-29 13:26 ` Matthieu Baerts
2023-06-29 15:17 ` Eric Van Hensbergen
2023-06-29 16:41 ` Matthieu Baerts
2023-06-29 17:04 ` Eric Van Hensbergen
2023-06-29 17:25 ` Matthieu Baerts
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='CAFkjPT=xrkc1UVVFO8Qt35iEUWDTY0MMKO+CxwosySZvpME5vQ@mail.gmail.com' \
--to=ericvh@kernel.org \
--cc=evanhensbergen@icloud.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=regressions@lists.linux.dev \
--cc=v9fs@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).