linux-kernel - Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130426220427.GE1433@mtj.dyndns.org>
Date:	Fri, 26 Apr 2013 15:04:27 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Sedat Dilek <sedat.dilek@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-bluetooth@...r.kernel.org,
	Marcel Holtmann <marcel@...tmann.org>,
	Gustavo Padovan <gustavo@...ovan.org>,
	Johan Hedberg <johan.hedberg@...il.com>,
	Linux PM List <linux-pm@...ts.linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

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.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/