[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b72d4821-d3e6-4b29-96c8-6acb1fc916a8@gmx.de>
Date: Wed, 17 Dec 2025 09:27:49 +0100
From: Ronald Warsow <rwarsow@....de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com, sudipm.mukherjee@...il.com,
conor@...nel.org, hargar@...rosoft.com, broonie@...nel.org,
achill@...ill.org, sr@...dewatkins.com
Subject: Re: [PATCH 6.18 000/614] 6.18.2-rc1 review
On 17.12.25 06:47, Greg Kroah-Hartman wrote:
> On Tue, Dec 16, 2025 at 05:06:56PM +0100, Ronald Warsow wrote:
>> Hi
>>
>> no regressions here on x86_64 (RKL, Intel 11th Gen. CPU), but *only* when
>> running GPU driver i915.
>>
>> with GPU driver xe I get here:
>>
>> [ 14.391631] rfkill: input handler disabled
>> [ 14.787149] ------------[ cut here ]------------
>> [ 14.787153] refcount_t: underflow; use-after-free.
>> [ 14.787167] WARNING: CPU: 10 PID: 2463 at lib/refcount.c:28
....
>> ====
>>
>> If I did the bisect correct, bisect-log:
>>
>> # status: waiting for both good and bad commits
>> # good: [25442251cbda7590d87d8203a8dc1ddf2c93de61] Linux 6.18.1
>> git bisect good 25442251cbda7590d87d8203a8dc1ddf2c93de61
>> # status: waiting for bad commit, 1 good commit known
>> # bad: [103c79e44ce7c81882928abab98b96517a8bce88] Linux 6.18.2-rc1
>> git bisect bad 103c79e44ce7c81882928abab98b96517a8bce88
>> # bad: [d32e7ccac8c6afc6a3a46fa4e7cdf0568ee919bd] drm/msm: Fix NULL pointer
>> dereference in crashstate_get_vm_logs()
>> git bisect bad d32e7ccac8c6afc6a3a46fa4e7cdf0568ee919bd
>
> Is this also an issue with 6.19-rc1? Are we missing something here?
>
6.19-rc1 is okay here
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists