From: Daniel Lezcano <daniel.lezcano@free•fr>
To: davem@davemloft•net
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH net-2.6] packet : remove init_net restriction
Date: Fri, 16 Apr 2010 17:04:28 +0200 [thread overview]
Message-ID: <4BC87C7C.4060407@free.fr> (raw)
In-Reply-To: <1271322674-21726-1-git-send-email-daniel.lezcano@free.fr>
Daniel Lezcano wrote:
> The af_packet protocol is used by Perl to do ioctls as reported by
> Stephane Riviere:
>
> "Net::RawIP relies on SIOCGIFADDR et SIOCGIFHWADDR to get the IP and MAC
> addresses of the network interface."
>
> But in a new network namespace these ioctl fail because it is disabled for
> a namespace different from the init_net_ns.
>
> These two lines should not be there as af_inet and af_packet are
> namespace aware since a long time now. I suppose we forget to remove these
> lines because we sent the af_packet first, before af_inet was supported.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@free•fr>
> Reported-by: Stephane Riviere <stephane.riviere@regis-dgac•net>
> ---
> net/packet/af_packet.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
> index cc90363..243946d 100644
> --- a/net/packet/af_packet.c
> +++ b/net/packet/af_packet.c
> @@ -2169,8 +2169,6 @@ static int packet_ioctl(struct socket *sock, unsigned int cmd,
> case SIOCGIFDSTADDR:
> case SIOCSIFDSTADDR:
> case SIOCSIFFLAGS:
> - if (!net_eq(sock_net(sk), &init_net))
> - return -ENOIOCTLCMD;
> return inet_dgram_ops.ioctl(sock, cmd, arg);
> #endif
>
>
Shall I send it against net-next-2.6 ?
Thanks
-- Daniel
next prev parent reply other threads:[~2010-04-16 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 9:11 [PATCH net-2.6] packet : remove init_net restriction Daniel Lezcano
2010-04-16 15:04 ` Daniel Lezcano [this message]
2010-04-16 20:23 ` David Miller
2010-04-16 22:41 ` David Miller
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=4BC87C7C.4060407@free.fr \
--to=daniel.lezcano@free$(echo .)fr \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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