All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	Mathias Rav <m@git.strova.dk>
Cc: linux-man@vger.kernel.org, Mathias Rav <mathias@scalgo.com>
Subject: Re: [patch] link.2: ERRORS: add ENOENT when target is deleted
Date: Thu, 26 Nov 2020 13:36:29 +0100	[thread overview]
Message-ID: <a91363d4-8f46-401a-e214-e93ada9f71aa@gmail.com> (raw)
In-Reply-To: <a99da26b-db18-8fa9-62ff-a33a2735f5e9@gmail.com>

Hi Mathias & Michael,

Please, see a fix below.

Cheers,

Alex

On 11/26/20 11:00 AM, Michael Kerrisk (man-pages) wrote:
> On 11/25/20 2:27 PM, Mathias Rav wrote:
>> Linux kernel commit aae8a97d3ec30788790d1720b71d76fd8eb44b73
>> (part of kernel release v2.6.39) added a check to disallow creating a
>> hardlink to an unlinked file.
>>
>> Signed-off-by: Mathias Rav <m@git.strova.dk>
> 
> Thanks, Matthias. Patch applied.
> 
>> ---
>> The manual page already describes the trick of using AT_SYMLINK_FOLLOW
>> as an alternative to AT_EMPTY_PATH, and for AT_EMPTY_PATH the manual
>> page already notes that it "will generally not work if the file has a
>> link count of zero". However, the precise error (ENOENT) is not mentioned,
>> and the error case isn't mentioned in the ERRORS section at all.
>>
>> This makes it easy to overlook the fact that the AT_SYMLINK_FOLLOW
>> trick on /proc/self/fd/NN won't work on deleted files, as evidenced by
>> the follow message (which turns up when googling "linkat deleted ENOENT"):
>> https://groups.google.com/g/linux.kernel/c/zZO4lqqwp64
> 
> I think the above piece is actually worth including in the
> commit message, so I added it.
> 
> Thanks,
> 
> Michael
> 
>>  man2/link.2 | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/man2/link.2 b/man2/link.2
>> index 1e7b2efd8..202119c6e 100644
>> --- a/man2/link.2
>> +++ b/man2/link.2
>> @@ -318,6 +318,10 @@ open(path, O_TMPFILE | O_EXCL, mode);
>>  .IP
>>  See
>>  .BR open (2).

+.TP

>> +.B ENOENT
>> +An attempt was made to link to a
>> +.I /proc/self/fd/NN
>> +file corresponding to a file that has been deleted.
>>  .TP
>>  .B ENOENT
>>  .I oldpath
>>
> 
> 

  reply	other threads:[~2020-11-26 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 13:27 [patch] link.2: ERRORS: add ENOENT when target is deleted Mathias Rav
2020-11-26 10:00 ` Michael Kerrisk (man-pages)
2020-11-26 12:36   ` Alejandro Colomar (man-pages) [this message]
2020-11-26 12:53     ` Michael Kerrisk (man-pages)

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=a91363d4-8f46-401a-e214-e93ada9f71aa@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=m@git.strova.dk \
    --cc=mathias@scalgo.com \
    --cc=mtk.manpages@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.