Date: Mon, 16 Oct 2017 22:24:34 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Cc: "fabian.freyer@physik.tu-berlin.de" <fabian.freyer@physik.tu-berlin.de> Subject: pfind_locked(pid) fails when in a jail? Message-ID: <YTOPR0101MB2172A4421C7B012A503230D5DD4F0@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
next in thread | raw e-mail | index | archive | help
Hi,
A problem w.r.t. the NFSv4 client's renew thread (nfscl) running up a lot o=
f CPU
when the NFSv4 mount is in a jail has been reported to the freebsd-stable@
mailing list.
I know nothing about jails, but when looking at the code, the most obvious
cause of this would be "pfind_locked(pid)" failing to find a process.
- Will a jail affect how pfind_locked() behaves?
- If the answer is "yes", then I need to know how to either...
1 - Make pfind_locked() work the same as when no jail exists.
OR
2 - A way for the Renew thread can determine that a jail will affect pfi=
nd_locked()
behaviour, so it can avoid this problem.
#1 is preferred, since #2 may not be 100% correct, although #2 would allow =
the
code to behave well for most cases. (The exception is a case where a file r=
emains
open for a long period of time, with different processes doing byte range l=
ocks on
the file.)
Thanks in advance for any help w.r.t. jail behaviour, rick=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB2172A4421C7B012A503230D5DD4F0>