public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
	Marek Lindner <mareklindner@neomailbox.ch>,
	netdev <netdev@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Kalle Valo <kvalo@codeaurora.org>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [B.A.T.M.A.N.] ibss.c backtrace when batman-adv adds wireless interface
Date: Wed, 03 Feb 2016 18:14:55 +0100	[thread overview]
Message-ID: <5257267.1LZJPcyIcQ@bentobox> (raw)
In-Reply-To: <CA+5PVA4HVjsEw+j+HMDzO0gnQb4xTRwbAu4H2do3MU41QWvOvw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

On Wednesday 03 February 2016 10:24:43 Josh Boyer wrote:
> Hi All,
> 
> We've had a user report the backtrace below when loading batman-adv on
> his machine.  It looks like the cfg80211 layer is complaining about a
> null bss returned, but I cannot tell if the rtlwifi driver or
> batman-adv is in error here.
> 
> Thoughts?

About the attachment "batman-adv oopses with kernel-4.3.4-300+debug". Sorry,
this was my fault and caused by an copy+paster error while adding some
lockdep_asserts. This caused too many lockdep reports. It was fixed a while
ago upstream in 008a37448707 ("batman-adv: Fix lockdep annotation of
batadv_tlv_container_remove").

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-02-03 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 15:24 [B.A.T.M.A.N.] ibss.c backtrace when batman-adv adds wireless interface Josh Boyer
2016-02-03 15:26 ` Josh Boyer
2016-02-03 15:41   ` Johannes Berg
2016-02-03 15:49     ` Josh Boyer
2016-02-03 17:09     ` Sven Eckelmann
2016-02-03 17:35       ` Sven Eckelmann
2016-02-03 17:14 ` Sven Eckelmann [this message]

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=5257267.1LZJPcyIcQ@bentobox \
    --to=sven@narfation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=netdev@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