netdev - Re: Problem with tun driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 16 Sep 2010 15:23:39 +0200
From:	Martín Ferrari <martin.ferrari@...il.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	netdev <netdev@...r.kernel.org>, Alina <aquereilhac@...il.com>,
	Mathieu Lacage <mathieu.lacage@...hia.inria.fr>
Subject: Re: Problem with tun driver

Hi Eric,

On Thu, Sep 16, 2010 at 15:16, Eric W. Biederman <ebiederm@...ssion.com> wrote:

> Is it possible all of the processes in the network namespace you have
> passed the tun dev into are dying, and thus destroying the network
> namespace the tun dev is in?

I thought that might be the case, but no, I still have a process
there, and from that I spawn an "ip link" that shows me that the tap
device still exists and it is up.

> It sounds like you are dealing with the network namespace death case,
> or that someone is closing your filedescriptor on you.

I also checked that, but no, nobody is closing it... To make things
more strange, this happens to me only when communicating with my slave
processes by a ssh to localhost (the filedescriptor is passed using
SCM_RIGHTS), but not when I fork directly, so at this point a timing
issue seems to be the only explanation. But it still does not make
sense, as some traffic gets exchanged correctly.

Thanks for your time.
-- 
Martín Ferrari
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html