Page MenuHomeFreeBSD

fix getfhat bug introduced by D18359
ClosedPublic

Authored by jack_gandi.net on Dec 10 2018, 3:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 11, 3:17 AM
Unknown Object (File)
Sat, Apr 11, 1:33 AM
Unknown Object (File)
Thu, Apr 9, 11:23 AM
Unknown Object (File)
Sun, Apr 5, 2:44 AM
Unknown Object (File)
Thu, Apr 2, 4:40 PM
Unknown Object (File)
Thu, Apr 2, 9:06 AM
Unknown Object (File)
Mon, Mar 30, 11:03 AM
Unknown Object (File)
Sat, Mar 14, 1:25 PM

Details

Summary

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

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 21475
Build 20791: arc lint + arc unit

Event Timeline

jack_gandi.net retitled this revision from Summary: review https://reviews.freebsd.org/D18359 introduced bug for getfhat(2) with NULL path. to review D18359 introduced bug forgetfhat(2) with NULL path..Dec 10 2018, 3:39 PM
jack_gandi.net retitled this revision from review D18359 introduced bug forgetfhat(2) with NULL path. to fix getfhat bug introduced by D18359.
jack_gandi.net 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.