From: David Miller <davem@davemloft.net>
To: PeterHuewe@gmx.de
Cc: yoshfuji@linux-ipv6.org, fengguang.wu@intel.com, netdev@vger.kernel.org
Subject: Re: Sparse Warnings: net/ipv6/route.c:521:17: sparse: context imbalance in 'rt6_probe' - different lock contexts for basic block
Date: Mon, 21 Jan 2013 15:48:03 -0500 (EST) [thread overview]
Message-ID: <20130121.154803.1415897555788515730.davem@davemloft.net> (raw)
In-Reply-To: <201301212103.18066.PeterHuewe@gmx.de>
From: Peter Hüwe <PeterHuewe@gmx.de>
Date: Mon, 21 Jan 2013 21:03:17 +0100
> Hi YOSHIFUJI,
>
> FYI, there are new sparse warnings show up in
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> branch: master
> head: 887c95cc1da53f66a5890fdeab13414613010097
> commit: 2152caea719657579daa3a1a57a5425a3db6d612 [185/189] ipv6: Do not depend
> on rt->n in rt6_probe().
>
>>> net/ipv6/route.c:521:17: sparse: context imbalance in 'rt6_probe' -
> different lock contexts for basic block
>
> On latest net-next/master it's
> net/ipv6/route.c:500:17: warning: context imbalance in 'rt6_probe' - different
> lock contexts for basic block
>
>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Reported-by: Peter Huewe <peterhuewe@gmx.de>
This is fixed by:
commit b820bb6b996966d93a5442b5fbf803ea58e7f487
Author: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Mon Jan 21 09:58:50 2013 +0000
ndisc: Do not try to update "updated" time if neighbour has already gone.
Commit 2152caea ("ipv6: Do not depend on rt->n in rt6_probe().")
introduce a bug to try to update "updated" time in neighbour
structure.
Update the "updated" time only if neighbour is available.
Bug was found by Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index 2d94d5a..f3328bc 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -492,10 +492,10 @@ static void rt6_probe(struct rt6_info *rt)
struct in6_addr mcaddr;
struct in6_addr *target;
- neigh->updated = jiffies;
-
- if (neigh)
+ if (neigh) {
+ neigh->updated = jiffies;
write_unlock(&neigh->lock);
+ }
target = (struct in6_addr *)&rt->rt6i_gateway;
addrconf_addr_solict_mult(target, &mcaddr);
next prev parent reply other threads:[~2013-01-21 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 20:03 Sparse Warnings: net/ipv6/route.c:521:17: sparse: context imbalance in 'rt6_probe' - different lock contexts for basic block Peter Hüwe
2013-01-21 20:48 ` David Miller [this message]
2013-01-21 20:56 ` Peter Hüwe
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=20130121.154803.1415897555788515730.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=PeterHuewe@gmx.de \
--cc=fengguang.wu@intel.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).