From mboxrd@z Thu Jan  1 00:00:00 1970
From: Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Probleam reading fdinfo symlinks after
 30a08bf2d31d275c6fc71dd1811342777e95c831
Date: Mon, 4 Jun 2012 19:14:07 +0400
Message-ID: <20120604151407.GD23701@moon>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: LKML <linux-kernel@vger.kernel.org>,
	LINUXFS-ML <linux-fsdevel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Eric Biederman <ebiederm@xmission.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

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@neptune~]# 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@neptune ~]# cat /proc/`pidof crond`/fdinfo/0
 | pos:	0
 | flags:	0100002

I suspect this is unintentional behaviour of the commit.