diff options
author | John Baldwin <jhb@FreeBSD.org> | 2017-12-19 22:39:05 +0000 |
---|---|---|
committer | John Baldwin <jhb@FreeBSD.org> | 2017-12-19 22:39:05 +0000 |
commit | b501cc5da6f8e10d354ace1befbf59737543eb30 (patch) | |
tree | ce6caa546b7b98b4b622de74c587481ca0a6b7c4 /usr.sbin/watch | |
parent | ff46fd16e53f4e3b70c7c5e816a8d62892a41e43 (diff) | |
download | src-b501cc5da6f8e10d354ace1befbf59737543eb30.tar.gz src-b501cc5da6f8e10d354ace1befbf59737543eb30.zip |
Rework pathconf handling for FIFOs.
On the one hand, FIFOs should respect other variables not supported by
the fifofs vnode operation (such as _PC_NAME_MAX, _PC_LINK_MAX, etc.).
These values are fs-specific and must come from a fs-specific method.
On the other hand, filesystems that support FIFOs are required to
support _PC_PIPE_BUF on directory vnodes that can contain FIFOs.
Given this latter requirement, once the fs-specific VOP_PATHCONF
method supports _PC_PIPE_BUF for directories, it is also suitable for
FIFOs permitting a single VOP_PATHCONF method to be used for both
FIFOs and non-FIFOs.
To that end, retire all of the FIFO-specific pathconf methods from
filesystems and change FIFO-specific vnode operation switches to use
the existing fs-specific VOP_PATHCONF method. For fifofs, set it's
VOP_PATHCONF to VOP_PANIC since it should no longer be used.
While here, move _PC_PIPE_BUF handling out of vop_stdpathconf() so that
only filesystems supporting FIFOs will report a value. In addition,
only report a valid _PC_PIPE_BUF for directories and FIFOs.
Discussed with: bde
Reviewed by: kib (part of a larger patch)
MFC after: 1 month
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D12572
Notes
Notes:
svn path=/head/; revision=327004
Diffstat (limited to 'usr.sbin/watch')
0 files changed, 0 insertions, 0 deletions