From: Christoph Hellwig <hch@infradead.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] flags parameter for linkat
Date: Sat, 25 Feb 2006 09:16:07 +0000 [thread overview]
Message-ID: <20060225091606.GA22749@infradead.org> (raw)
In-Reply-To: <200602231410.k1NEAMk1021578@devserv.devel.redhat.com>
On Thu, Feb 23, 2006 at 09:10:22AM -0500, Ulrich Drepper wrote:
> I'm currently at the POSIX meeting and one thing covered was the
> incompatibility of Linux's link() with the POSIX definition. The
> difference is the treatment of symbolic links in the destination
> name. Linux does not follow symlinks, POSIX requires it does.
>
> Even 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?
Please stop adding these crappy flags argument everywhere, they're also
creaping like a cancer through the other *at stuff. Just make linkat
do the righ thing per posix spec for link, and then you can implement
a posix link based on it in glibc if the user compiles with XOPEN_SOURCE
or whatever.
next prev parent reply other threads:[~2006-02-25 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 14:10 [PATCH] flags parameter for linkat Ulrich Drepper
2006-02-23 14:19 ` David Vrabel
2006-02-23 20:26 ` Ralf Baechle
2006-02-25 9:16 ` Christoph Hellwig [this message]
2006-02-25 10:13 ` 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=20060225091606.GA22749@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--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