Page MenuHomeFreeBSD

fix getfhat bug introduced by D18359

Authored by on Dec 10 2018, 3:34 PM.
Referenced Files
Unknown Object (File)
Oct 29 2023, 8:07 AM
Unknown Object (File)
Oct 29 2023, 1:11 AM
Unknown Object (File)
Oct 24 2023, 5:04 AM
Unknown Object (File)
Oct 23 2023, 11:19 AM
Unknown Object (File)
Sep 16 2023, 1:46 PM
Unknown Object (File)
Sep 5 2023, 2:19 PM
Unknown Object (File)
Jul 19 2023, 6:29 PM
Unknown Object (File)
Jun 29 2023, 2:26 AM



. path is part of kernel address space, should use UIO_SYSSPACE and not UIO_USERSPACE.

Diff Detail

rS FreeBSD src repository - subversion
Lint Not Applicable
Tests Not Applicable

Event Timeline retitled this revision from Summary: review introduced bug for getfhat(2) with NULL path. to review D18359 introduced bug forgetfhat(2) with NULL path..Dec 10 2018, 3:39 PM retitled this revision from review D18359 introduced bug forgetfhat(2) with NULL path. to fix getfhat bug introduced by D18359. edited the summary of this revision. (Show Details)

I clearly missed this in the original commit. Why do you need this special-case 'dot' behaviour ? Why cannot getfhat() behave same as openat(2) WRT NULL path ?

The dot special behaviour was because our application is currently using getfhat with a NULL path. We'll fix this in the application rather than in kernel code. I've rolled back to a behaviour similar to openat, also amended the manpage.

This revision is now accepted and ready to land.Dec 10 2018, 5:25 PM
This revision was automatically updated to reflect the committed changes.