From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] FWD: batman: potential null dereference
Date: Mon, 8 Mar 2010 23:21:02 +0800 [thread overview]
Message-ID: <201003082321.03064.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20100308151244.GA4468@lunn.ch>
On Monday 08 March 2010 23:12:44 Andrew Lunn wrote:
> Does somebody have time to look at this?
As far as I understand the question is: What happens if
!orig_node->router && !neigh_node go into update_route() ?
Fairly easy to answer: Only update_routes() (note the "s") calls
update_route() which checks for this case:
if (orig_node->router != neigh_node)
update_route()
Not very obvious though ...
Regards,
Marek
PS: Can we somehow better communicate that we have a mailing list for these
kind of questions ?
prev parent reply other threads:[~2010-03-08 15:21 UTC|newest]
Thread overview: 6+ 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
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 [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=201003082321.03064.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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.