From: Andrew Lunn <andrew@lunn.ch>
To: "B.A.T.M.A.N" <b.a.t.m.a.n@lists.open-mesh.net>
Subject: [B.A.T.M.A.N.] FWD: batman: potential null dereference
Date: Mon, 8 Mar 2010 16:12:44 +0100 [thread overview]
Message-ID: <20100308151244.GA4468@lunn.ch> (raw)
Does somebody have time to look at this?
Andrew
----- Forwarded message from Dan Carpenter <error27@gmail.com> -----
Date: Mon, 8 Mar 2010 16:07:01 +0300
From: Dan Carpenter <error27@gmail.com>
To: andrew@lunn.ch
Cc: kernel-janitors@vger.kernel.org
Subject: batman: potential null dereference
X-Spam-Status: No, score=2.9 required=4.0 tests=BAYES_00,FREEMAIL_FROM,
RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_WEB autolearn=no
version=3.3.0
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.
regards,
dan carpenter
----- End forwarded message -----
next reply other threads:[~2010-03-08 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 15:12 Andrew Lunn [this message]
2010-03-08 15:15 ` [B.A.T.M.A.N.] FWD: batman: potential null dereference Sven Eckelmann
2010-03-08 16:11 ` Dan Carpenter
2010-03-08 16:23 ` Sven Eckelmann
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=20100308151244.GA4468@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.