linux-kernel - Probleam reading fdinfo symlinks after 30a08bf2d31d275c6fc71dd1811342777e95c831

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

Date:	Mon, 4 Jun 2012 19:14:07 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	LINUXFS-ML <linux-fsdevel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Eric Biederman <ebiederm@...ssion.com>
Subject: Probleam reading fdinfo symlinks after
 30a08bf2d31d275c6fc71dd1811342777e95c831

Hi Linus,

just tried 3.5-rc1 out and found that with commit
30a08bf2d31d275c6fc71dd1811342777e95c831 the reading
of fdinfo files returns "Too many levels of symbolic links"
error.

 | [root@...tune~]# cat /proc/`pidof crond`/fdinfo/0
 | cat: /proc/1417/fdinfo/0: Too many levels of symbolic links

so I reverted it manually and now it works as expected

 | [root@...tune ~]# cat /proc/`pidof crond`/fdinfo/0
 | pos:	0
 | flags:	0100002

I suspect this is unintentional behaviour of the commit.
--
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/