[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11114.1260090546@jrobl>
Date: Sun, 06 Dec 2009 18:09:06 +0900
From: hooanon05@...oo.co.jp
To: Al Viro <viro@...IV.linux.org.uk>
Cc: linux-kernel@...r.kernel.org, stewb@...ux-foundation.org
Subject: Re: [RFC 0/5] pathconf(3) with _PC_LINK_MAX
Al Viro:
> Um... Why do we need that, again? Note that there is no way whatsoever
> for predicting whether link(2) will fail due to having too many existing
> links before you attempt the call - links can be created or removed between
> stat(2) and link(2). So any uses of that value are heuristical.
>
> Can you actually show any use cases of that thing? Preferably - in existing
> code, but even a theoretical one would be interesting.
Thanx for quick reply.
To be honest, I am unsure how important this is in real world.
But I've met (reported, precisly) such test program. It seems to come
from old X/Open, though the actual reporter tried the LSB (Linux
Standard Base) runtime-test.
You can get the source code from
ftp.freestandards.org/pub/lsb/test_suites/released-3.2/source/runtime/lsb-test-core-3.2.0-2.src.rpm
+ lsb-test-core-3.2.0.tar.gz
+ lts_vsx-pcts-3.2.0.tgz
+ tset/POSIX.os/files/link/link.c
Here I quote just a part from tset/POSIX.os/files/link/link.c,
The function tblink() behaves as a wrapper for link(2) with the error
checking.
When the filesystem is unknown to pathconf(_PC_LINK_MAX), 'link_max' may
be incorrect and LSB cannot pass this test.
test15()
{
creat(t15a_file, MODEANY);
link_max = pathconf(t15a_file, _PC_LINK_MAX);
/* create lesser of LINK_MAX and PCTS_LINK_MAX links successfully */
/* i.e. make (testmax-1) link() calls, as there is 1 link already */
testmax = link_max;
for (i = 0; i < testmax-1; i++)
{
(void) sprintf(links[i], "L%ld", i+1);
if (tblink(t15a_file, links[i], SUCCEED, NOERROR) != SUCCEED)
break;
}
/* if LINK_MAX is testable, next link gives EMLINK */
(void) tblink(t15a_file, t15b_file, SYSERROR, EMLINK);
}
J. R. Okajima
--
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/
Powered by blists - more mailing lists