diff options
author | Ulrich Drepper <drepper@redhat.com> | 2006-02-24 13:04:21 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-02-24 14:31:39 -0800 |
commit | c04030e16dbea2f7581f82cc6688695927f6ac5b (patch) | |
tree | 7ff5cd2494a133f1bf571f7af02e656bb01d124f /mm | |
parent | ee713059d4922e4ee17700496d9eb3b95b1ab836 (diff) | |
download | linux-3.10-c04030e16dbea2f7581f82cc6688695927f6ac5b.tar.gz linux-3.10-c04030e16dbea2f7581f82cc6688695927f6ac5b.tar.bz2 linux-3.10-c04030e16dbea2f7581f82cc6688695927f6ac5b.zip |
[PATCH] flags parameter for linkat
I'm currently at the POSIX meeting and one thing covered was the
incompatibility of Linux's link() with the POSIX definition. The name.
Linux does not follow symlinks, POSIX requires it does.
Even if somebody thinks this is a good default behavior we cannot change this
because it would break the ABI. But the fact remains that some application
might want this behavior.
We have one chance to help implementing this without breaking the behavior.
For this we could use the new linkat interface which would need a new
flags parameter. If the new parameter is AT_SYMLINK_FOLLOW the new
behavior could be invoked.
I do not want to introduce such a patch now. But we could add the
parameter now, just don't use it. The patch below would do this. Can we
get this late patch applied before the release more or less fixes the
syscall API?
Signed-off-by: Ulrich Drepper <drepper@redhat.com>
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions