Messages in this thread | | | Date | Sat, 27 Apr 2013 01:24:48 +0200 | Subject | Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ] | From | Sedat Dilek <> |
| |
On Sat, Apr 27, 2013 at 12:04 AM, Tejun Heo <tj@kernel.org> wrote: > On Fri, Apr 26, 2013 at 11:07:44PM +0200, Sedat Dilek wrote: >> > The second argument %rsi is zero, which got transferred to %r13 and >> > then offset deref on it trapped. >> > >> > The second argument is @wq and the oopsing code is the wq->flags deref >> > in the following if condition. >> > >> > /* if dying, only works from the same workqueue are allowed */ >> > if (unlikely(wq->flags & __WQ_DRAINING) && >> > WARN_ON_ONCE(!is_chained_work(wq))) >> > return; >> > >> > So, umm, don't pass in NULL as @wq. :) >> > >> >> Do you have a patch for this? > > Heh, I haven't even looked at the caller. It's a bug on the workqueue > user side. >
[ CC Frederic ]
You should explain that a bit.
I have tested with my "problematic -3" kernel and did not see the warning again. So, I assume it's independent of linux-dynticks kconfig-settings.
- Sedat -
> Thanks. > > -- > tejun
| |