From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Salvatore Bonaccorso <carnil@debian.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
"Jitindar Singh, Suraj" <surajjs@amazon.com>
Cc: "rohiths.msft@gmail.com" <rohiths.msft@gmail.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"stfrench@microsoft.com" <stfrench@microsoft.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"pc@manguebit.com" <pc@manguebit.com>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"nspmangalore@gmail.com" <nspmangalore@gmail.com>,
"willy@infradead.org" <willy@infradead.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>,
stable@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [Regression 6.1.y] From "cifs: Fix flushing, invalidation and file size with copy_file_range()"
Date: Sat, 6 Jan 2024 13:02:16 +0100 [thread overview]
Message-ID: <13a70cc5-78fc-49a4-8d78-41e5479e3023@leemhuis.info> (raw)
In-Reply-To: <ZZk6qA54A-KfzmSz@eldamar.lan>
On 06.01.24 12:34, Salvatore Bonaccorso wrote:
> On Sat, Jan 06, 2024 at 11:40:58AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
>>
>> Does this problem also happen in mainline, e.g. with 6.7-rc8?
>
> Thanks a lot for replying back. So far I can tell, the regression is
> in 6.1.y only
Ahh, good to know, thx!
> For this reason I added to regzbot only "regzbot ^introduced
> 18b02e4343e8f5be6a2f44c7ad9899b385a92730" which is the commit in
> v6.1.68.
Which was the totally right thing to do, thx. Guess I sooner or later
will add something like "#regzbot tag notinmainline" to avoid the
ambiguity we just cleared up, but maybe that's overkill.
Ciao, Thorsten!
next prev parent reply other threads:[~2024-01-06 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2023121124-trifle-uncharted-2622@gregkh>
[not found] ` <a76b370f93cb928c049b94e1fde0d2da506dfcb2.camel@amazon.com>
2024-01-05 20:50 ` [Regression 6.1.y] From "cifs: Fix flushing, invalidation and file size with copy_file_range()" Salvatore Bonaccorso
2024-01-06 10:40 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-06 11:34 ` Salvatore Bonaccorso
2024-01-06 12:02 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-01-10 16:20 ` Salvatore Bonaccorso
2024-01-11 11:03 ` gregkh
2024-01-12 8:12 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-12 14:25 ` David Howells
2024-01-13 5:20 ` Steve French
2024-01-13 8:47 ` gregkh
2024-01-13 9:31 ` Salvatore Bonaccorso
2024-01-13 9:41 ` gregkh
2024-01-14 3:23 ` Steve French
2024-01-13 17:02 ` Matthew Wilcox
[not found] ` <CAH2r5mvN1F0PqeyAQqv8Z__FikYV+3kekVP0yTtLmCmzmg=QGA@mail.gmail.com>
2024-01-13 17:51 ` Matthew Wilcox
2024-01-13 20:38 ` Greg KH
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=13a70cc5-78fc-49a4-8d78-41e5479e3023@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=carnil@debian.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nspmangalore@gmail.com \
--cc=pc@manguebit.com \
--cc=regressions@lists.linux.dev \
--cc=rohiths.msft@gmail.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=surajjs@amazon.com \
--cc=willy@infradead.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 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).