From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: REGRESSION on linux-next (next-20251125)
Date: Thu, 27 Nov 2025 18:16:05 +0530 [thread overview]
Message-ID: <78e1b97d-837f-48e9-882f-8320473ec9bb@intel.com> (raw)
In-Reply-To: <20251127-kaktus-gourmet-626cff3d8314@brauner>
On 11/27/2025 4:13 PM, Christian Brauner wrote:
> I just pushed:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs-6.19.fd_prepare
>
> If you want to test that, please.
aah! only the sync_file.c change you suggested was not fixing the issue.
But with [1] on top of linux-next, the issue is now resolved.
It also solves another issue[2] we bisected (before I could report it to
you, which is never a bad thing)
Thank you.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/commit/?h=vfs-6.19.fd_prepare&id=bf44cb6382f90fbda2eeae67065dc9401a967485
[2]
https://intel-gfx-ci.01.org/tree/linux-next/next-20251125/bat-mtlp-8/igt@core_hotunplug@unbind-rebind.html
==
Chaitanya
next prev parent reply other threads:[~2025-11-27 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 6:05 REGRESSION on linux-next (next-20251125) Borah, Chaitanya Kumar
2025-11-27 9:27 ` Christian Brauner
2025-11-27 9:33 ` Borah, Chaitanya Kumar
2025-11-27 10:43 ` Christian Brauner
2025-11-27 12:46 ` Borah, Chaitanya Kumar [this message]
2025-11-27 14:23 ` Christian Brauner
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=78e1b97d-837f-48e9-882f-8320473ec9bb@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=brauner@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=suresh.kumar.kurmi@intel.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