Fixed commit message and applied to drm-misc-fixes
On 4/25/2025 11:36 AM, Jacek Lawrynowicz wrote:
> From: Karol Wachowski
>
> The mutex unlock for vdev->submitted_jobs_lock was incorrectly placed
> after unlocking file_priv->lock. Change order of unlocks to avoid potential
> race conditions.
>
On 4/29/2025 2:41 AM, Jacek Lawrynowicz wrote:
Hi,
On 4/28/2025 4:21 PM, Jeff Hugo wrote:
On 4/28/2025 12:47 AM, Jacek Lawrynowicz wrote:
Hi,
On 4/25/2025 7:22 PM, Jeff Hugo wrote:
On 4/25/2025 3:36 AM, Jacek Lawrynowicz wrote:
From: Karol Wachowski
The mutex unlock for vdev->submitted_jo
Hi,
On 4/28/2025 4:21 PM, Jeff Hugo wrote:
> On 4/28/2025 12:47 AM, Jacek Lawrynowicz wrote:
>> Hi,
>>
>> On 4/25/2025 7:22 PM, Jeff Hugo wrote:
>>> On 4/25/2025 3:36 AM, Jacek Lawrynowicz wrote:
From: Karol Wachowski
The mutex unlock for vdev->submitted_jobs_lock was incorrectly p
On 4/28/2025 12:47 AM, Jacek Lawrynowicz wrote:
Hi,
On 4/25/2025 7:22 PM, Jeff Hugo wrote:
On 4/25/2025 3:36 AM, Jacek Lawrynowicz wrote:
From: Karol Wachowski
The mutex unlock for vdev->submitted_jobs_lock was incorrectly placed
after unlocking file_priv->lock. Change order of unlocks to av
Hi,
On 4/25/2025 7:22 PM, Jeff Hugo wrote:
> On 4/25/2025 3:36 AM, Jacek Lawrynowicz wrote:
>> From: Karol Wachowski
>>
>> The mutex unlock for vdev->submitted_jobs_lock was incorrectly placed
>> after unlocking file_priv->lock. Change order of unlocks to avoid potential
>
> This should read "be
On 4/25/2025 3:36 AM, Jacek Lawrynowicz wrote:
From: Karol Wachowski
The mutex unlock for vdev->submitted_jobs_lock was incorrectly placed
after unlocking file_priv->lock. Change order of unlocks to avoid potential
This should read "before unlocking", right?
race conditions.
Fixes: 5bbccad
From: Karol Wachowski
The mutex unlock for vdev->submitted_jobs_lock was incorrectly placed
after unlocking file_priv->lock. Change order of unlocks to avoid potential
race conditions.
Fixes: 5bbccadaf33e ("accel/ivpu: Abort all jobs after command queue
unregister")
Signed-off-by: Karol Wachows
