Re: ✗ Fi.CI.BUILD: failure for Regression on linux-next (next-20250120) (rev2)

2025-01-30 Thread Jani Nikula
On Wed, 29 Jan 2025, Al Viro wrote: > On Wed, Jan 29, 2025 at 08:53:37PM -, Patchwork wrote: >> == Series Details == >> >> Series: Regression on linux-next (next-20250120) (rev2) >> URL : https://patchwork.freedesktop.org/series/143978/ >> State : failure

Re: Regression on linux-next (next-20250120)

2025-01-30 Thread Greg Kroah-Hartman
gt; > g...@lists.freedesktop.org; intel...@lists.freedesktop.org; Kurmi, Suresh > > Kumar ; Saarinen, Jani > > ; linux-fsde...@vger.kernel.org; Alexander Gordeev > > > > Subject: Re: Regression on linux-next (next-20250120) > > > > On Wed, Jan 29, 2025 at 07:19:37PM +, Al

RE: Regression on linux-next (next-20250120)

2025-01-30 Thread Borah, Chaitanya Kumar
-fsde...@vger.kernel.org; Alexander Gordeev > > Subject: Re: Regression on linux-next (next-20250120) > > On Wed, Jan 29, 2025 at 07:19:37PM +, Al Viro wrote: > > On Wed, Jan 29, 2025 at 08:13:02AM +0100, Greg Kroah-Hartman wrote: > > > > > > Both are needed,

Re: Regression on linux-next (next-20250120)

2025-01-29 Thread Greg Kroah-Hartman
On Wed, Jan 29, 2025 at 07:19:37PM +, Al Viro wrote: > On Wed, Jan 29, 2025 at 08:13:02AM +0100, Greg Kroah-Hartman wrote: > > > > Both are needed, actually. Slightly longer term I would rather > > > split full_proxy_{read,write,lseek}() into short and full variant, > > > getting rid of the "

Re: ✗ Fi.CI.BUILD: failure for Regression on linux-next (next-20250120) (rev2)

2025-01-29 Thread Al Viro
On Wed, Jan 29, 2025 at 08:53:37PM -, Patchwork wrote: > == Series Details == > > Series: Regression on linux-next (next-20250120) (rev2) > URL : https://patchwork.freedesktop.org/series/143978/ > State : failure > > == Summary == > > Error: patch > https:/

✗ Fi.CI.BUILD: failure for Regression on linux-next (next-20250120) (rev2)

2025-01-29 Thread Patchwork
== Series Details == Series: Regression on linux-next (next-20250120) (rev2) URL : https://patchwork.freedesktop.org/series/143978/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/143978/revisions/2/mbox/ not applied Applying: Regression on linux

Re: Regression on linux-next (next-20250120)

2025-01-29 Thread Al Viro
On Wed, Jan 29, 2025 at 08:13:02AM +0100, Greg Kroah-Hartman wrote: > > Both are needed, actually. Slightly longer term I would rather > > split full_proxy_{read,write,lseek}() into short and full variant, > > getting rid of the "check which pointer is non-NULL" and killed > > the two remaining u

Re: Regression on linux-next (next-20250120)

2025-01-28 Thread Greg Kroah-Hartman
On Wed, Jan 29, 2025 at 04:37:12AM +, Al Viro wrote: > On Tue, Jan 28, 2025 at 04:00:58PM +, Borah, Chaitanya Kumar wrote: > > > Unfortunately this change does not help us. I think it is the methods > > member that causes the problem. So the following change solves the problem > > for us

Re: Regression on linux-next (next-20250120)

2025-01-28 Thread Al Viro
On Tue, Jan 28, 2025 at 04:00:58PM +, Borah, Chaitanya Kumar wrote: > Unfortunately this change does not help us. I think it is the methods member > that causes the problem. So the following change solves the problem for us. > > > --- a/fs/debugfs/file.c > +++ b/fs/debugfs/file.c > @@ -102,

RE: Regression on linux-next (next-20250120)

2025-01-28 Thread Borah, Chaitanya Kumar
rinen, Jani > ; linux-fsde...@vger.kernel.org; Alexander Gordeev > > Subject: Re: Regression on linux-next (next-20250120) > > On Sun, Jan 26, 2025 at 04:54:55PM +0100, Alexander Gordeev wrote: > > > > > Since the version next-20250120 [2], we are seeing the following &

✗ Fi.CI.BUILD: failure for Regression on linux-next (next-20250120)

2025-01-26 Thread Patchwork
== Series Details == Series: Regression on linux-next (next-20250120) URL : https://patchwork.freedesktop.org/series/143978/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/143978/revisions/1/mbox/ not applied Applying: Regression on linux-next

Re: Regression on linux-next (next-20250120)

2025-01-26 Thread Al Viro
On Sun, Jan 26, 2025 at 04:54:55PM +0100, Alexander Gordeev wrote: > > > Since the version next-20250120 [2], we are seeing the following > > > regression > > > > Ugh... To narrow the things down, could you see if replacing > > fsd = kmalloc(sizeof(*fsd), GFP_KERNEL); > > with >

Re: Regression on linux-next (next-20250120)

2025-01-26 Thread Alexander Gordeev
On Thu, Jan 23, 2025 at 06:18:53PM +, Al Viro wrote: Hi Al, > On Thu, Jan 23, 2025 at 03:41:08PM +, Borah, Chaitanya Kumar wrote: > > Hello Al, > > > > Hope you are doing well. I am Chaitanya from the linux graphics team in > > Intel. > > > > This mail is regarding a regression we are

RE: Regression on linux-next (next-20250120)

2025-01-24 Thread Borah, Chaitanya Kumar
.kernel.org > Subject: Re: Regression on linux-next (next-20250120) > > On Thu, Jan 23, 2025 at 03:41:08PM +, Borah, Chaitanya Kumar wrote: > > Hello Al, > > > > Hope you are doing well. I am Chaitanya from the linux graphics team in > Intel. > > > > Thi

Re: Regression on linux-next (next-20250120)

2025-01-23 Thread Al Viro
On Thu, Jan 23, 2025 at 03:41:08PM +, Borah, Chaitanya Kumar wrote: > Hello Al, > > Hope you are doing well. I am Chaitanya from the linux graphics team in Intel. > > This mail is regarding a regression we are seeing in our CI runs[1] on > linux-next repository. > > Since the version next-2

Regression on linux-next (next-20250120)

2025-01-23 Thread Borah, Chaitanya Kumar
Hello Al, Hope you are doing well. I am Chaitanya from the linux graphics team in Intel. This mail is regarding a regression we are seeing in our CI runs[1] on linux-next repository. Since the version next-20250120 [2], we are seeing the following regression ```