netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next:master 195/198] net/bridge/br_mdb.c:79:35: sparse: incompatible types in comparison expression (different address spaces)
Date: Mon, 10 Dec 2012 20:36:44 +0800	[thread overview]
Message-ID: <1355143004.11752.19.camel@cr0> (raw)
In-Reply-To: <50c3fd5e.qB65a7/5e+IZT2ix%fengguang.wu@intel.com>

On Sun, 2012-12-09 at 10:54 +0800, kbuild test robot wrote:
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> head:   9ecb9aabaf634677c77af467f4e3028b09d7bcda
> commit: ee07c6e7a6f8a25c18f0a6b18152fbd7499245f6 [195/198] bridge: export multicast database via netlink
> 
> 
> sparse warnings:
> 
> + net/bridge/br_mdb.c:79:35: sparse: incompatible types in comparison expression (different address spaces)

Hi, Fengguang,

I am not sure if I understand this warning correctly. Does the following
patch fix it?

Thanks!

---------------->

diff --git a/net/bridge/br_mdb.c b/net/bridge/br_mdb.c
index 2528328..0bc0e13 100644
--- a/net/bridge/br_mdb.c
+++ b/net/bridge/br_mdb.c
@@ -77,7 +77,7 @@ static int br_mdb_fill_info(struct sk_buff *skb,
struct netlink_callback *cb,
                        }
 
                        for (pp = &mp->ports;
-                            (p = rcu_dereference(*pp)) != NULL;
+                            (p = rcu_dereference_protected(*pp, 1)) !=
NULL;
                              pp = &p->next) {
                                port = p->port;
                                if (port) {

  reply	other threads:[~2012-12-10 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09  2:54 [net-next:master 195/198] net/bridge/br_mdb.c:79:35: sparse: incompatible types in comparison expression (different address spaces) kbuild test robot
2012-12-10 12:36 ` Cong Wang [this message]
2012-12-10 12:44   ` Cong Wang

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=1355143004.11752.19.camel@cr0 \
    --to=amwang@redhat.com \
    --cc=fengguang.wu@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).