From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: "B.A.T.M.A.N" <b.a.t.m.a.n@lists.open-mesh.net>
Cc: Dan Carpenter <error27@gmail.com>
Subject: Re: [B.A.T.M.A.N.] FWD: batman: potential null dereference
Date: Mon, 8 Mar 2010 16:15:30 +0100 [thread overview]
Message-ID: <201003081615.49579.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <20100308151244.GA4468@lunn.ch>
[-- Attachment #1: Type: Text/Plain, Size: 1429 bytes --]
Andrew Lunn wrote:
> Does somebody have time to look at this?
> ----- Forwarded message from Dan Carpenter <error27@gmail.com> -----
[...]
> drivers/staging/batman-adv/routing.c
> 88 } else if ((orig_node->router == NULL) && (neigh_node !=
> NULL)) { ^^^^^^^^^^^^^^^^^^^^^^^^^
> 89
> 90 bat_dbg(DBG_ROUTES,
> 91 "Adding route towards: %pM (via %pM)\n",
> 92 orig_node->orig, neigh_node->addr);
> 93 hna_global_add_orig(orig_node, hna_buff,
> hna_buff_len); 94
> 95 /* route changed */
> 96 } else {
> 97 bat_dbg(DBG_ROUTES, "Changing route towards: %pM
> (now via %pM - was via %pM)\n", orig_node->orig, neigh_node->addr,
> orig_node->router->addr);
> ^^^^^^^^^^^^^^^^^^^^^^^
> 98 }
>
> This could fail if debugging is enabled and neigh_node is null.
It looks a little bit like checked with clang's static analyzer. This analyzer
has problems to track constraints at all. This means that it doesn't catch the
update_routes constraint "orig_node->router != neigh_node".
But I am also not good at tracking that kind of constraints and reported this
or a similar "bug" in batmand a while ago.
So it is not a real bug, but maybe not easy to read.
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-08 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 15:12 [B.A.T.M.A.N.] FWD: batman: potential null dereference Andrew Lunn
2010-03-08 15:15 ` Sven Eckelmann [this message]
2010-03-08 16:11 ` Dan Carpenter
2010-03-08 16:23 ` Sven Eckelmann
2010-03-08 15:21 ` Marek Lindner
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=201003081615.49579.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=error27@gmail.com \
/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