linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, "David Spinadel" <dvdspndl@gmail.com>
Subject: Re: BUG: problem while tracing cfg80211
Date: Mon, 18 Mar 2013 23:09:41 +0100	[thread overview]
Message-ID: <514790A5.90004@broadcom.com> (raw)
In-Reply-To: <51478F06.9000506@broadcom.com>

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



  reply	other threads:[~2013-03-18 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 19:47 BUG: problem while tracing cfg80211 Arend van Spriel
2013-03-18 20:03 ` Johannes Berg
2013-03-18 22:02   ` Arend van Spriel
2013-03-18 22:09     ` Arend van Spriel [this message]
2013-03-19  8:18       ` Johannes Berg
2013-03-19  9:01         ` Arend van Spriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=514790A5.90004@broadcom.com \
    --to=arend@broadcom.com \
    --cc=dvdspndl@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).