From: Ulrich Drepper <drepper@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, torvalds@osdl.org
Subject: [PATCH] Implement AT_SYMLINK_FOLLOW flag for linkat
Date: Sat, 17 Jun 2006 15:13:22 -0400 [thread overview]
Message-ID: <200606171913.k5HJDM3U021408@devserv.devel.redhat.com> (raw)
When the linkat() syscall was added the flag parameter was added in the
last minute but it wasn't used so far. The following patch should
change that. My tests show that this is all that's needed.
If OLDNAME is a symlink setting the flag causes linkat to follow the
symlink and create a hardlink with the target. This is actually
the behavior POSIX demands for link() as well but Linux wisely does
not do this. With this flag (which will most likely be in the next
POSIX revision) the programmer can choose the behavior, defaulting
to the safe variant. As a side effect it is now possible to implement
a POSIX-compliant link(2) function for those who are interested.
touch file
ln -s file symlink
linkat(fd, "symlink", fd, "newlink", 0)
-> newlink is hardlink of symlink
linkat(fd, "symlink", fd, "newlink", AT_SYMLINK_FOLLOW)
-> newlink is hardlink of file
The value of AT_SYMLINK_FOLLOW is determined by the definition we
already use in glibc.
Signed-Off-By: Ulrich Drepper <drepper@redhat.com>
fs/namei.c | 6 ++++--
include/linux/fcntl.h | 1 +
2 files changed, 5 insertions(+), 2 deletions(-)
--- linux/fs/namei.c-follow 2006-06-17 11:22:39.000000000 -0700
+++ linux/fs/namei.c 2006-06-17 11:58:18.000000000 -0700
@@ -2243,14 +2243,16 @@
int error;
char * to;
- if (flags != 0)
+ if ((flags & ~AT_SYMLINK_FOLLOW) != 0)
return -EINVAL;
to = getname(newname);
if (IS_ERR(to))
return PTR_ERR(to);
- error = __user_walk_fd(olddfd, oldname, 0, &old_nd);
+ error = __user_walk_fd(olddfd, oldname,
+ flags & AT_SYMLINK_FOLLOW ? LOOKUP_FOLLOW : 0,
+ &old_nd);
if (error)
goto exit;
error = do_path_lookup(newdfd, to, LOOKUP_PARENT, &nd);
--- linux/include/linux/fcntl.h-follow 2006-06-17 11:24:21.000000000 -0700
+++ linux/include/linux/fcntl.h 2006-06-17 11:24:51.000000000 -0700
@@ -29,6 +29,7 @@
#define AT_SYMLINK_NOFOLLOW 0x100 /* Do not follow symbolic links. */
#define AT_REMOVEDIR 0x200 /* Remove directory instead of
unlinking file. */
+#define AT_SYMLINK_FOLLOW 0x400 /* Follow symbolic links. */
#ifdef __KERNEL__
next reply other threads:[~2006-06-17 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 19:13 Ulrich Drepper [this message]
2006-06-18 19:16 ` Al Viro
2006-06-18 19:22 ` Linus Torvalds
2006-06-18 19:32 ` Al Viro
2006-06-18 19:40 ` Ulrich Drepper
2006-06-18 22:06 ` Al Viro
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=200606171913.k5HJDM3U021408@devserv.devel.redhat.com \
--to=drepper@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome