Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932236Ab3EOMsx (ORCPT ); Wed, 15 May 2013 08:48:53 -0400 Received: from mail3.vodafone.ie ([213.233.128.45]:62929 "EHLO mail3.vodafone.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932215Ab3EOMsk (ORCPT ); Wed, 15 May 2013 08:48:40 -0400 X-Greylist: delayed 590 seconds by postgrey-1.27 at vger.kernel.org; Wed, 15 May 2013 08:48:40 EDT X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjkDAKCAk1FtTvCU/2dsb2JhbAANNBqDPkSCeL0SAwGBD4MTAQEBBCMPAT8HEAsNCwICBRYLAgIJAwIBAgFFEwEHAQGIDwUzqhNykUSBJo0ZXwcWgiyBEwOYXIUXhV6IMA Message-ID: <519381D8.5080206@draigBrady.com> Date: Wed, 15 May 2013 13:38:48 +0100 From: =?UTF-8?B?UMOhZHJhaWcgQnJhZHk=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: linux-kernel@vger.kernel.org CC: Eric Blake Subject: Re: RFC: allow empty symlink targets References: <1358427833-3847-1-git-send-email-P@draigBrady.com> <50F8252C.2060404@draigBrady.com> In-Reply-To: <50F8252C.2060404@draigBrady.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1434 Lines: 32 On 01/17/2013 04:22 PM, Pádraig Brady wrote: > On 01/17/2013 01:03 PM, Pádraig Brady wrote: >> The discussion leading to this is at http://bugs.gnu.org/13447 >> In summary other systems allow an empty target for a symlink, >> and POSIX specifies that it should be allowed? > > In relation to this, Eric Blake said: > >> In today's Austin Group meeting, I was tasked to open a new bug that >> would state specifically how the empty symlink is resolved; the intent >> is to allow both Solaris behavior (current directory) and BSD behavior >> (ENOENT). Meanwhile, everyone was in agreement that the Linux kernel >> has a bug for rejecting the creation of an empty symlink, but once that >> bug is fixed, then Linux can choose either Solaris or BSD behavior for >> how to resolve such a symlink. >> >> It will probably be a bug report similar to this one, which regarded how >> to handle a symlink containing just slashes: >> http://austingroupbugs.net/view.php?id=541 Following up from http://austingroupbugs.net/view.php?id=649 It seems POSIX will now allow the current Linux behavior of returning ENOENT, or the Solaris behavior of allowing empty symlink targets. cheers, Pádraig. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/