From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
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>
Subject: Probleam reading fdinfo symlinks after 30a08bf2d31d275c6fc71dd1811342777e95c831
Date: Mon, 4 Jun 2012 19:14:07 +0400 [thread overview]
Message-ID: <20120604151407.GD23701@moon> (raw)
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.
next reply other threads:[~2012-06-04 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 15:14 Cyrill Gorcunov [this message]
2012-06-04 17:59 ` Probleam reading fdinfo symlinks after 30a08bf2d31d275c6fc71dd1811342777e95c831 Linus Torvalds
2012-06-04 18:11 ` Cyrill Gorcunov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120604151407.GD23701@moon \
--to=gorcunov@openvz.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.