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: <1351250734.16863.26.camel@twins>
Date:	Fri, 26 Oct 2012 13:25:34 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Ingo Molnar <mingo@...hat.com>, Tejun Heo <tj@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: lockdep info message

On Fri, 2012-10-26 at 12:15 +0200, Arend van Spriel wrote:
> Hi Peter and/or Ingo,
> 
> I am working on a driver (brcmfmac) and when unloading it or unplugging 
> the device I get this info message (see below) upon calling 
> cancel_work_sync(). Just wondering if there is something I need to do in 
> the driver or should it be done in workqueue code.

Your driver, as that's the one allocating the struct work_struct thingy.

You've either failed to use INIT_WORK() or need to use
INIT_WORK_ONSTACK() if that's appropriate. It looks like you could have
used DECLARE*_WORK inside a function or something similar.

Anyway, without the driver code present I can't really say much more.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ