From: David Miller <davem@davemloft.net>
To: jan.kiszka@web.de
Cc: linux-kernel@vger.kernel.org,
i4ldeveloper@listserv.isdn4linux.de, netdev@vger.kernel.org,
isdn@linux-pingi.de, peterz@infradead.org
Subject: Re: [PATCH v2] CAPI: Silence lockdep warning on get_capi_appl_by_nr usage
Date: Thu, 21 Oct 2010 04:29:59 -0700 (PDT) [thread overview]
Message-ID: <20101021.042959.91336397.davem@davemloft.net> (raw)
In-Reply-To: <4CBB13B7.8080705@web.de>
From: Jan Kiszka <jan.kiszka@web.de>
Date: Sun, 17 Oct 2010 17:18:15 +0200
> As long as we hold capi_controller_lock, we can safely access
> capi_applications without RCU protection as no one can modify the
> application list underneath us. Introduce an RCU-free
> __get_capi_appl_by_nr for this purpose. This silences lockdep warnings
> on suspicious rcu_dereference usage.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
Applied.
prev parent reply other threads:[~2010-10-21 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 11:14 [PATCH] CAPI: Silence lockdep warning on get_capi_appl_by_nr usage Jan Kiszka
2010-10-17 10:25 ` Peter Zijlstra
2010-10-17 15:18 ` [PATCH v2] " Jan Kiszka
2010-10-21 11:29 ` David Miller [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=20101021.042959.91336397.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=jan.kiszka@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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).