From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mms2.broadcom.com ([216.31.210.18]:2316 "EHLO mms2.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652Ab3CRWJw (ORCPT ); Mon, 18 Mar 2013 18:09:52 -0400 Message-ID: <514790A5.90004@broadcom.com> (sfid-20130318_230956_678758_4C3D9405) Date: Mon, 18 Mar 2013 23:09:41 +0100 From: "Arend van Spriel" MIME-Version: 1.0 To: "Johannes Berg" cc: linux-wireless@vger.kernel.org, "David Spinadel" Subject: Re: BUG: problem while tracing cfg80211 References: <51476F35.9040909@broadcom.com> <1363636984.8260.17.camel@jlt4.sipsolutions.net> <51478F06.9000506@broadcom.com> In-Reply-To: <51478F06.9000506@broadcom.com> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 03/18/2013 11:02 PM, Arend van Spriel wrote: > On 03/18/2013 09:03 PM, Johannes Berg wrote: >> On Mon, 2013-03-18 at 20:47 +0100, Arend van Spriel wrote: >>> Hi Johannes, >>> >>> While testing David Spinadel's P2P device support functionality I got >>> the following blurb, which is probably caused by cfg80211 tracing given >>> the instruction pointer address. >>> >>> brcmfmac returns ERR_PTR(-ENOENT) and I think the trace code/macros do >>> not take this into account. >> >> I guess this should fix it? >> >> http://p.sipsolutions.net/fdea39f2a56aff67.txt > > Did not test it, but that would be my guess to. Just another > observation: Is the wdev identifier not defined as u64? Found the answer. In nl80211 API the wdev identifier is 64 bits, which got me confused. Gr. AvS