linux-kernel - Re: New system call wanted: fdreopen

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ka2h4v$ra3$2@ger.gmane.org>
Date:	Sun, 9 Dec 2012 17:18:23 +0000 (UTC)
From:	Tristan Wibberley <tristan.wibberley@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: New system call wanted: fdreopen

On Sun, 09 Dec 2012 11:27:46 -0500, Theodore Ts'o wrote:

> On Sun, Dec 09, 2012 at 03:03:30PM +0000, Tristan Wibberley wrote:
>> 
>> - /proc/self/fd/* does not solve this problem because the file might no

...

> Actually, /proc/self/fd/* _will_ work.  When you do a ls -l, it looks
> like a symlink, but the files in /proc/self/fd (and /proc/<pid>/fd more
> generally) are magic.  If you open files in /proc/<pid>/fd/*, it will do
> what you want.

Oh! Cool! By reading how to solve this class of problem with google 
search results I couldn't find any indication that /proc/pid/fd/* worked 
differently than a symlink.

Thanks for your quick reply.

-- 
Tristan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/