Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 11:08:01AM -0800, Dmitry Torokhov wrote: > On Tue, Dec 15, 2015 at 11:00 AM, Gustavo Padovan wrote: > > 2015-12-15 Daniel Vetter : > > > >> On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote: > >> > Userspace can close the

Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 09:22:56AM -0800, Dmitry Torokhov wrote: > On Tue, Dec 15, 2015 at 5:30 AM, Gustavo Padovan wrote: > > 2015-12-14 Dmitry Torokhov : > > > >> Userspace can close the sync device while there are still active fence > >> points, in which

Re: [PATCH] android: fix warning when releasing active sync point

Op 15-12-15 om 18:19 schreef Dmitry Torokhov: > On Tue, Dec 15, 2015 at 2:01 AM, Maarten Lankhorst > wrote: >> Op 15-12-15 om 02:29 schreef Dmitry Torokhov: >>> Userspace can close the sync device while there are still active fence >>> points, in which case

Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 1:26 AM, Daniel Vetter wrote: > On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote: >> Userspace can close the sync device while there are still active fence >> points, in which case kernel produces the following warning: >> >> [ 43.853176]

Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 2:01 AM, Maarten Lankhorst wrote: > Op 15-12-15 om 02:29 schreef Dmitry Torokhov: >> Userspace can close the sync device while there are still active fence >> points, in which case kernel produces the following warning: >> >> [

Re: [PATCH] android: fix warning when releasing active sync point

2015-12-15 Daniel Vetter : > On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote: > > Userspace can close the sync device while there are still active fence > > points, in which case kernel produces the following warning: > > > > [ 43.853176] [ cut here

Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 5:50 AM, Frank Binns wrote: > Is this not the issue fixed by 8e43c9c75? No because if we start teardown without waiting for the fence to be signaled it will still be on the active_list. Thanks. -- Dmitry -- To unsubscribe from this list: send

Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 5:30 AM, Gustavo Padovan wrote: > 2015-12-14 Dmitry Torokhov : > >> Userspace can close the sync device while there are still active fence >> points, in which case kernel produces the following warning: >> >> [ 43.853176]

Re: [PATCH] android: fix warning when releasing active sync point

On Tue, Dec 15, 2015 at 11:00 AM, Gustavo Padovan wrote: > 2015-12-15 Daniel Vetter : > >> On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote: >> > Userspace can close the sync device while there are still active fence >> > points, in which case

Re: [PATCH] android: fix warning when releasing active sync point

On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote: > Userspace can close the sync device while there are still active fence > points, in which case kernel produces the following warning: > > [ 43.853176] [ cut here ] > [ 43.857834] WARNING: CPU: 0 PID:

Re: [PATCH] android: fix warning when releasing active sync point

Op 15-12-15 om 02:29 schreef Dmitry Torokhov: > Userspace can close the sync device while there are still active fence > points, in which case kernel produces the following warning: > > [ 43.853176] [ cut here ] > [ 43.857834] WARNING: CPU: 0 PID: 892 at >

Re: [PATCH] android: fix warning when releasing active sync point

Is this not the issue fixed by 8e43c9c75? Thanks Frank On 15/12/15 13:30, Gustavo Padovan wrote: > 2015-12-14 Dmitry Torokhov : > >> Userspace can close the sync device while there are still active fence >> points, in which case kernel produces the following warning: >> >> [

Re: [PATCH] android: fix warning when releasing active sync point

2015-12-14 Dmitry Torokhov : > Userspace can close the sync device while there are still active fence > points, in which case kernel produces the following warning: > > [ 43.853176] [ cut here ] > [ 43.857834] WARNING: CPU: 0 PID: 892 at >

[PATCH] android: fix warning when releasing active sync point

Userspace can close the sync device while there are still active fence points, in which case kernel produces the following warning: [ 43.853176] [ cut here ] [ 43.857834] WARNING: CPU: 0 PID: 892 at