diff options
author | jhb <jhb@FreeBSD.org> | 2013-02-21 19:02:50 +0000 |
---|---|---|
committer | jhb <jhb@FreeBSD.org> | 2013-02-21 19:02:50 +0000 |
commit | ca1e2e0739fbad3590a92aca668f4659d9e48b52 (patch) | |
tree | 089655cb610bf1daca917a806eaed3dfb2554455 /sys/netinet6/in6_src.c | |
parent | 42e7ffdbc0cbb18e0dd9c588a2b26d27773a90a1 (diff) | |
download | FreeBSD-src-ca1e2e0739fbad3590a92aca668f4659d9e48b52.zip FreeBSD-src-ca1e2e0739fbad3590a92aca668f4659d9e48b52.tar.gz |
Further refine the handling of stop signals in the NFS client. The
changes in r246417 were incomplete as they did not add explicit calls to
sigdeferstop() around all the places that previously passed SBDRY to
_sleep(). In addition, nfs_getcacheblk() could trigger a write RPC from
getblk() resulting in sigdeferstop() recursing. Rather than manually
deferring stop signals in specific places, change the VFS_*() and VOP_*()
methods to defer stop signals for filesystems which request this behavior
via a new VFCF_SBDRY flag. Note that this has to be a VFC flag rather than
a MNTK flag so that it works properly with VFS_MOUNT() when the mount is
not yet fully constructed. For now, only the NFS clients are set this new
flag in VFS_SET().
A few other related changes:
- Add an assertion to ensure that TDF_SBDRY doesn't leak to userland.
- When a lookup request uses VOP_READLINK() to follow a symlink, mark
the request as being on behalf of the thread performing the lookup
(cnp_thread) rather than using a NULL thread pointer. This causes
NFS to properly handle signals during this VOP on an interruptible
mount.
PR: kern/176179
Reported by: Russell Cattelan (sigdeferstop() recursion)
Reviewed by: kib
MFC after: 1 month
Diffstat (limited to 'sys/netinet6/in6_src.c')
0 files changed, 0 insertions, 0 deletions