Bug 168814

Summary: [patch] remove `d` negative pointer EINVAL requirement from read(2)
Product: Documentation Reporter: Enji Cooper <ngie>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description Enji Cooper freebsd_committer freebsd_triage 2012-06-07 17:30:16 UTC 
The read(2) requirement that states that...

"     [EINVAL]           The pointer associated with d was negative.
"

.. is bogus based on my code inspection of sys_generic.c and kern_descrip.c (and the comment is misleading -- d isn't a pointer, but maybe the comment was referring to a kernel implementation item with file descriptor objects *shrugs*).

Fix: Patch attached with submission follows:
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2012-07-01 16:50:10 UTC 
Responsible Changed
From-To: freebsd-doc->eadler

I'll take it.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2012-09-02 17:52:45 UTC 
Responsible Changed
From-To: eadler->freebsd-doc

I won't be looking at this PR for a while and I need to clear some out 
of my queue
Comment 3 Bryan Drewery freebsd_committer freebsd_triage 2014-03-27 10:56:50 UTC 
State Changed
From-To: open->closed

It looks like uiomove() will return EINVAL on negative offset, and I did 
find tmpfs_read returning EINVAL on negative offset as well.