On Sat, Oct 28, 2017 at 11:07:28AM +0800, Li Bin wrote:
> When queue_work() is used in irq (not in task context), there is
> a potential case that trigger NULL pointer dereference.
>
> worker_thread()
> |-spin_lock_irq()
>
On Sat, Oct 28, 2017 at 11:07:28AM +0800, Li Bin wrote:
> When queue_work() is used in irq (not in task context), there is
> a potential case that trigger NULL pointer dereference.
>
> worker_thread()
> |-spin_lock_irq()
>
On Sat, Oct 28, 2017 at 11:07 AM, Li Bin wrote:
> When queue_work() is used in irq (not in task context), there is
> a potential case that trigger NULL pointer dereference.
>
> worker_thread()
>
On Sat, Oct 28, 2017 at 11:07 AM, Li Bin wrote:
> When queue_work() is used in irq (not in task context), there is
> a potential case that trigger NULL pointer dereference.
>
> worker_thread()
> |-spin_lock_irq()
>
When queue_work() is used in irq (not in task context), there is
a potential case that trigger NULL pointer dereference.
worker_thread()
|-spin_lock_irq()
|-process_one_work()
|-worker->current_pwq = pwq
When queue_work() is used in irq (not in task context), there is
a potential case that trigger NULL pointer dereference.
worker_thread()
|-spin_lock_irq()
|-process_one_work()
|-worker->current_pwq = pwq
6 matches
Mail list logo