On 1/11/24 04:13, Iago Toral wrote:
Ok, thanks for checking, you can add my R-B on the original patch then.
Applied to drm-misc/drm-misc-next-fixes!
Best Regards,
- Maíra
Iago
El mié, 10-01-2024 a las 07:42 -0300, Maira Canal escribió:
Hi Iago,
On 1/10/24 03:48, Iago Toral wrote:
I thin
Ok, thanks for checking, you can add my R-B on the original patch then.
Iago
El mié, 10-01-2024 a las 07:42 -0300, Maira Canal escribió:
> Hi Iago,
>
> On 1/10/24 03:48, Iago Toral wrote:
> > I think this is fine, but I was wondering if it would be simpler
> > and
> > easier to just remove the s
Hi Iago,
On 1/10/24 03:48, Iago Toral wrote:
I think this is fine, but I was wondering if it would be simpler and
easier to just remove the sched cleanup from v3d_job_init and instead
always rely on callers to eventually call v3d_job_cleanup for fail
paths, where we are already calling v3d_job_c
I think this is fine, but I was wondering if it would be simpler and
easier to just remove the sched cleanup from v3d_job_init and instead
always rely on callers to eventually call v3d_job_cleanup for fail
paths, where we are already calling v3d_job_cleanup.
Iago
El mar, 09-01-2024 a las 11:28 -0
Currently, if `v3d_job_init()` fails (e.g. in the IGT test "bad-in-sync",
where we submit an invalid in-sync to the IOCTL), then we end up with
the following NULL pointer dereference:
[ 34.146279] Unable to handle kernel NULL pointer dereference at virtual
address 0078
[ 34.146301
