smbfs does not implement UIO_NOCOPY (zerocopy) and if receives request for such will return with error and set errno to EOPNOTSUPP, which was until now undocumented. This means that many popular web and ftp servers which implement sendfile(2) could have problems when serving files from smbfs mounts if they not have handling for this case and fallback to another method, but as the errno code was undocumented probably there are not much as of now. Fix: none How-To-Repeat: Mount some smbfs share to a directory that is served for example with the www/lighttpd port. Trying to download them via http will result in 0 byte documents.
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
This PR can be closed : src/lib/libc/sys/sendfile.2 Revision 1.29: download - view: text, markup, annotated - select for diffs Mon Oct 31 04:08:28 2005 UTC (7 years, 1 month ago) by jkoshy Branches: MAIN Diff to: previous 1.28: preferred, colored Changes since revision 1.28: +5 -0 lines Document the fact that sendfile(2) can EOPNOTSUPP if the underlying filesystem for the file being transferred doesn't support UIO_NOCOPY. Reported by: Niki Denev <nike_d@cytexbg.com>
State Changed From-To: open->closed Per submitter request