Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Mar 2018 07:55:50 -0800
From:      Christoph Hellwig <hch@infradead.org>
To:        "Robert N. M. Watson" <robert.watson@cl.cam.ac.uk>
Cc:        Justin Cormack <justin@specialbusservice.com>, "<cl-capsicum-discuss@lists.cam.ac.uk>" <cl-capsicum-discuss@lists.cam.ac.uk>,  freebsd-hackers@freebsd.org, Mariusz Zaborski <oshogbo@freebsd.org>
Subject:   Re: [capsicum] unlinkfd
Message-ID:  <20180305155550.GA22789@infradead.org>
In-Reply-To: <17DE0BFF-42A2-4CD7-B09C-ABA2606C4041@cl.cam.ac.uk>
References:  <20180302183514.GA99279@x-wing> <CAK4o1Wyk54chHobhUkb2PBUtaWOF2rDv6tkX_bFGY6D331xUqw@mail.gmail.com> <17DE0BFF-42A2-4CD7-B09C-ABA2606C4041@cl.cam.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
With my Linux hat I'd much prefer using the AT_EMPTY_PATH flag that
Linux already supports for a few *at calls to operate on the dirfd
fd.  But it seems like neither FreeBSD nor anyone else picked up that
flag, so it might be a bit of a hard sell.

FreeBSD bugzilla related to AT_EMPTY_PATH and the lack of it for
unlinkat even in Linux:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197778

Linux bugzilla:

https://bugzilla.kernel.org/show_bug.cgi?id=93441

If you are interested in bringing this to FreeBSD that might be reason
enough for me into looking into a Linux implementation as well.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180305155550.GA22789>