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
F131755823: D31530.diff
Fri, Oct 10, 10:15 PM
Unknown Object (File)
Fri, Oct 3, 1:15 AM
Unknown Object (File)
Mon, Sep 29, 11:37 PM
Unknown Object (File)
Thu, Sep 25, 1:10 AM
Unknown Object (File)
Wed, Sep 24, 9:03 AM
Unknown Object (File)
Sun, Sep 21, 6:10 AM
Unknown Object (File)
Sun, Sep 14, 4:15 PM
Unknown Object (File)
Aug 27 2025, 7:29 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.