Page MenuHomeFreeBSD

fstatat(2): handle non-vnode file descriptors for AT_EMPTY_PATH
ClosedPublic

Authored by kib on Aug 13 2021, 5:56 PM.
Tags
None
Referenced Files
F111042031: D31530.diff
Wed, Feb 26, 2:49 PM
Unknown Object (File)
Thu, Feb 13, 1:24 PM
Unknown Object (File)
Wed, Feb 12, 2:12 AM
Unknown Object (File)
Jan 14 2025, 12:56 PM
Unknown Object (File)
Dec 31 2024, 10:53 AM
Unknown Object (File)
Nov 22 2024, 12:52 AM
Unknown Object (File)
Nov 20 2024, 1:43 PM
Unknown Object (File)
Nov 20 2024, 6:41 AM
Subscribers
None

Details

Summary

Set NIRES_EMPTYPATH earlies, to have use of EMPTYPATH recorded even if we are going to return error. When namei_setup() refused to accept dirfd, which is not vnode type, and indicated by ENOTDIR error return, fall back to kern_fstat(dirfd).

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kib requested review of this revision.Aug 13 2021, 5:56 PM
kib created this revision.

When does this scenario arise?

This revision is now accepted and ready to land.Aug 13 2021, 8:36 PM

When does this scenario arise?

For instance, fstatat(pipefd, "", &stat, AT_EMPTY_PATH) would do it. I have no idea why an app would want to call fstat(pipefd) this way, but this is what Dmitry' test case does, adopted from some Linux trace.