summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1998-04-06 17:44:40 +0000
committerpeter <peter@FreeBSD.org>1998-04-06 17:44:40 +0000
commitb2396f73c8710efb65637f3f7213aa672c908615 (patch)
tree74d5e9c4e048ec49008bb8a8eb9b35d1e38f894f /lib/libc
parentd5ab1c3759352a4180dfc28b7952eeb389bb3261 (diff)
downloadFreeBSD-src-b2396f73c8710efb65637f3f7213aa672c908615.zip
FreeBSD-src-b2396f73c8710efb65637f3f7213aa672c908615.tar.gz
Don't panic if a VOP_READ() gets through on a short link, Just Do It
(because we can :-). This means you can open a link file (or pseudo-file in the case of short links where the data is stored in the inode rather than disk blocks) and read the contents. However, trap any writes from the user as it's difficult to do the right thing in all cases. A link may be short and the user may be trying to extend it beyond the limit and so on. Although.. being able to re-target a symlink without deleting it first might have been nice. This stuff is a bit perverse since symlink() and readlink() calls can end up actually being implemented as read/write vnode ops. Reviewed by: phk
Diffstat (limited to 'lib/libc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud