public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batman-adv: Set special lockdep classes to avoid lockdep warning
Date: Fri, 24 Aug 2012 23:42:46 +0200	[thread overview]
Message-ID: <201208242342.46630.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1345446239-5115-1-git-send-email-sven@narfation.org>

On Monday, August 20, 2012 09:03:59 Sven Eckelmann wrote:
> Transmissions over batman-adv devices always start another nested
> transmission over devices attached to the batman-adv interface. These
> devices usually use the ethernet lockdep class for the tx_queue lock which
> is also set by default for all batman-adv devices. Lockdep will detect a
> nested locking attempt of two locks with the same class and warn about a
> possible deadlock.
> 
> This is the default and expected behavior and should not alarm the locking
> correctness prove mechanism. Therefore, the locks for all netdevice
> specific tx queues get a special batman-adv lock class to avoid a false
> positive for each transmission.
> 
> Reported-by: Linus Lüssing <linus.luessing@web.de>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> * fixed comment style
> * fixed commit message
> 
>  soft-interface.c |   21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)

Applied in revision e27bb6f.

Thanks,
Marek

      reply	other threads:[~2012-08-24 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19  7:29 [B.A.T.M.A.N.] [RFC] batman-adv: Set special lockdep classes to avoid lockdep warning Sven Eckelmann
2012-08-19  7:57 ` Simon Wunderlich
2012-08-19 23:22 ` [B.A.T.M.A.N.] [PATCH] " Sven Eckelmann
2012-08-20  7:00   ` Sven Eckelmann
2012-08-20  7:03   ` [B.A.T.M.A.N.] [PATCHv2] " Sven Eckelmann
2012-08-24 21:42     ` Marek Lindner [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=201208242342.46630.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.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