Re: [PATCH 5.10 082/133] drm/v3d: Ensure job pointer is set to NULL after job completion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Greg,

On 30/01/25 13:26, Greg Kroah-Hartman wrote:
On Thu, Jan 30, 2025 at 12:56:25PM -0300, Maíra Canal wrote:
Hi Greg,

This patch introduced a race-condition that was fixed in
6e64d6b3a3c39655de56682ec83e894978d23412 ("drm/v3d: Assign job pointer
to NULL before signaling the fence") - already in torvalds/master. Is it
possible to push the two patches together? This way we wouldn't break
any devices.

As all 5.15 and newer devices are broken right now, that's not good :(

I agree, it's terrible. I'm currently waiting for stable to pick up the
fix (as it is quite quick, thanks for the great work). For a even
quicker solution, should I send the fix for the newer stable branches or
you can queue 6e64d6b3a3c39655de56682ec83e894978d23412 directly?

I added the "Fixes:" tag to the fix and CCed stable.

Best Regards,
- Maíra


If possible, same thing for 5.4.

Ok, let me queue it up now, thanks.

greg k-h





[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux