From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Brian Haley <brian.haley@hp.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, containers <containers@lists.osdl.org>
Subject: Re: [PATCH 0/2] netns: fix for NULL-dereference in ipv6 code
Date: Thu, 14 Aug 2008 16:17:07 -0400 [thread overview]
Message-ID: <48A492C3.7080502@hp.com> (raw)
In-Reply-To: <48A48717.4020609@hp.com>
Brian Haley wrote:
> Hi,
>
> When fixing the NULL-dereference of the idev in rt6_fill_node(), I
> noticed that dev_net() doesn't handle a NULL argument either. These two
> patches fix that, as well as add a network namespace argument to
> rt6_fill_node() and ipv6_dev_get_saddr().
Brian
What is the reason that dev_net() would need to handle a NULL arg?
I think a NULL pointer in dev_net is a bug if Network Namespaces are used.
-vlad
prev parent reply other threads:[~2008-08-14 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 19:27 [PATCH 0/2] netns: fix for NULL-dereference in ipv6 code Brian Haley
2008-08-14 20:17 ` Vlad Yasevich [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=48A492C3.7080502@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=brian.haley@hp.com \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--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).