Hi Sasha,
The 5.10.y kernel backported commit 80df83c2c57e ("mmc: core: add devm_mmc_alloc_host") but not the fix for it.
71d04535e853 ("mmc: core: fix return value check in devm_mmc_alloc_host()")
The 6.6.y kernel was released with both commits so it's not affected and none of the other stable trees include the buggy commit so they're not affected either. Only 5.10.y needs to be fixed.
regards, dan carpenter
Hi Sasha,
On 15/11/24 19:59, Dan Carpenter wrote:
Hi Sasha,
The 5.10.y kernel backported commit 80df83c2c57e ("mmc: core: add devm_mmc_alloc_host") but not the fix for it.
71d04535e853 ("mmc: core: fix return value check in devm_mmc_alloc_host()")
The 6.6.y kernel was released with both commits so it's not affected and none of the other stable trees include the buggy commit so they're not affected either. Only 5.10.y needs to be fixed.
How come we have a commit in 5.10.y and 6.6.y and not in 6.1.y and 5.15.y -- May be we should detect those.
Thanks, Harshit
regards, dan carpenter
On Fri, Nov 15, 2024 at 09:35:28PM +0530, Harshit Mogalapalli wrote:
Hi Sasha,
On 15/11/24 19:59, Dan Carpenter wrote:
Hi Sasha,
The 5.10.y kernel backported commit 80df83c2c57e ("mmc: core: add devm_mmc_alloc_host") but not the fix for it.
71d04535e853 ("mmc: core: fix return value check in devm_mmc_alloc_host()")
The 6.6.y kernel was released with both commits so it's not affected and none of the other stable trees include the buggy commit so they're not affected either. Only 5.10.y needs to be fixed.
How come we have a commit in 5.10.y and 6.6.y and not in 6.1.y and 5.15.y -- May be we should detect those.
We used to detect them, something seems to have gone wrong...
On Fri, Nov 15, 2024 at 09:35:28PM +0530, Harshit Mogalapalli wrote:
Hi Sasha,
On 15/11/24 19:59, Dan Carpenter wrote:
Hi Sasha,
The 5.10.y kernel backported commit 80df83c2c57e ("mmc: core: add devm_mmc_alloc_host") but not the fix for it.
71d04535e853 ("mmc: core: fix return value check in devm_mmc_alloc_host()")
The 6.6.y kernel was released with both commits so it's not affected and none of the other stable trees include the buggy commit so they're not affected either. Only 5.10.y needs to be fixed.
How come we have a commit in 5.10.y and 6.6.y and not in 6.1.y and 5.15.y -- May be we should detect those.
This was added because it was a dependancy, that's how things got out of sync...
On Fri, Nov 15, 2024 at 05:29:38PM +0300, Dan Carpenter wrote:
Hi Sasha,
The 5.10.y kernel backported commit 80df83c2c57e ("mmc: core: add devm_mmc_alloc_host") but not the fix for it.
71d04535e853 ("mmc: core: fix return value check in devm_mmc_alloc_host()")
The 6.6.y kernel was released with both commits so it's not affected and none of the other stable trees include the buggy commit so they're not affected either. Only 5.10.y needs to be fixed.
Now queued up, thanks.
greg k-h
linux-stable-mirror@lists.linaro.org
-
Dan Carpenter -
Greg KH -
Harshit Mogalapalli