On Mon, Feb 11, 2019 at 8:26 AM Robin van der Gracht wrote:
>
> Looks good
>
> Acked-by: Robin van der Gracht
Thanks all! I will send this for -rc7.
Cheers,
Miguel
On Sat, 9 Feb 2019 01:15:22 +0100
Miguel Ojeda wrote:
> On module unload/remove, we need to ensure that work does not run
> after we have freed resources. Concretely, cancel_delayed_work()
> may return while the callback function is still running.
>
> From kernel/workqueue.c:
>
> The work c
On Fri, Feb 8, 2019 at 7:15 PM Miguel Ojeda
wrote:
>
> On module unload/remove, we need to ensure that work does not run
> after we have freed resources. Concretely, cancel_delayed_work()
> may return while the callback function is still running.
>
> From kernel/workqueue.c:
>
> The work callb
On Sat, Feb 09, 2019 at 01:15:22AM +0100, Miguel Ojeda wrote:
> On module unload/remove, we need to ensure that work does not run
> after we have freed resources. Concretely, cancel_delayed_work()
> may return while the callback function is still running.
>
> From kernel/workqueue.c:
>
> The
On module unload/remove, we need to ensure that work does not run
after we have freed resources. Concretely, cancel_delayed_work()
may return while the callback function is still running.
>From kernel/workqueue.c:
The work callback function may still be running on return,
unless it return
5 matches
Mail list logo