* /proc/net/ symlink interacts badly with threads (Re: Procfs race condition bug)
[not found] <20140704101311.GA7020@glue.grepular.com>
@ 2014-07-07 13:41 ` One Thousand Gnomes
0 siblings, 0 replies; only message in thread
From: One Thousand Gnomes @ 2014-07-07 13:41 UTC (permalink / raw)
To: Mike Cardwell; +Cc: linux-kernel, netdev
On Fri, 4 Jul 2014 11:13:11 +0100
Mike Cardwell <linux@lists.grepular.com> wrote:
> I originally posted this two years ago (*) but received no response. I
> just had a look and the problem still exists on the 3.14 kernel I am
> currently running.
>
> I *think* I've uncovered a race condition bug in procfs. If I attempt to
I don't think you have found a race condition.
/proc/net/tcp is a symbolic link to /proc/self/net/tcp
Your thread does an open of /proc/net/tcp, which is a symlink
to /proc/self/net/tcp. If your thread id matches your process id then all
will be as you expect, if not then all will be pear shaped.
As far as I can see the code is doing precisely what it should do. It's
just that the use of the symlink when namespaces were added produces some
rather odd effects.
It's certainly a bug. It used to work, it's sensible it should work.
Added netdev
Alan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-07-07 13:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20140704101311.GA7020@glue.grepular.com>
2014-07-07 13:41 ` /proc/net/ symlink interacts badly with threads (Re: Procfs race condition bug) One Thousand Gnomes
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).