FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=releng%2F6.3 2005-02-18T18:32:32Z 2005-02-18T18:32:32Z John Baldwin jhb@FreeBSD.org 2005-02-18T18:32:32Z urn:sha1:f4b3589bdbea5f5d1abbb1c0896bbcff9552d977 exec_copyin_args(), kern_execve(), and exec_free_args() rather than execve() to eliminate stackgap use from Alpha's linux_execve(). Silence on: alpha@ 2004-11-27T06:51:39Z David Schultz das@FreeBSD.org 2004-11-27T06:51:39Z urn:sha1:6004362e66b76f04a5b994af40067c600da40d0a including other headers. 2004-09-01T02:11:28Z Julian Elischer julian@FreeBSD.org 2004-09-01T02:11:28Z urn:sha1:2630e4c90c7b775eb0248be7594a699839363dda where they are coming from and what is expected from them. MFC after: 2 days 2004-02-04T21:52:57Z John Baldwin jhb@FreeBSD.org 2004-02-04T21:52:57Z urn:sha1:91d5354a2ce810d848eca6ecf9da1027aeb2be6d - struct plimit includes a mutex to protect a reference count. The plimit structure is treated similarly to struct ucred in that is is always copy on write, so having a reference to a structure is sufficient to read from it without needing a further lock. - The proc lock protects the p_limit pointer and must be held while reading limits from a process to keep the limit structure from changing out from under you while reading from it. - Various global limits that are ints are not protected by a lock since int writes are atomic on all the archs we support and thus a lock wouldn't buy us anything. - All accesses to individual resource limits from a process are abstracted behind a simple lim_rlimit(), lim_max(), and lim_cur() API that return either an rlimit, or the current or max individual limit of the specified resource from a process. - dosetrlimit() was renamed to kern_setrlimit() to match existing style of other similar syscall helper functions. - The alpha OSF/1 compat layer no longer calls getrlimit() and setrlimit() (it didn't used the stackgap when it should have) but uses lim_rlimit() and kern_setrlimit() instead. - The svr4 compat no longer uses the stackgap for resource limits calls, but uses lim_rlimit() and kern_setrlimit() instead. - The ibcs2 compat no longer uses the stackgap for resource limits. It also no longer uses the stackgap for accessing sysctl's for the ibcs2_sysconf() syscall but uses kernel_sysctl() instead. As a result, ibcs2_sysconf() no longer needs Giant. - The p_rlimit macro no longer exists. Submitted by: mtm (mostly, I only did a few cleanups and catchups) Tested on: i386 Compiled on: alpha, amd64 2003-06-10T17:02:51Z David E. O'Brien obrien@FreeBSD.org 2003-06-10T17:02:51Z urn:sha1:f59584cd7f45da1aed72e454662a2a6628353f3e 2003-04-22T18:23:49Z John Baldwin jhb@FreeBSD.org 2003-04-22T18:23:49Z urn:sha1:fe8cdcae8755884de5038365ebd6730c32cbc1bd kern_sigprocmask() in the various binary compatibility emulators. - Replace calls to sigsuspend(), sigaltstack(), sigaction(), and sigprocmask() that used the stackgap with calls to the corresponding kern_sig*() functions instead without using the stackgap. 2003-04-18T20:54:41Z John Baldwin jhb@FreeBSD.org 2003-04-18T20:54:41Z urn:sha1:9eb78fcfd9da959c8d7acdb3163a17cc18de7710 minor cleanups in both. 2003-04-16T20:05:42Z John Baldwin jhb@FreeBSD.org 2003-04-16T20:05:42Z urn:sha1:e68c51ed5dde6374e215d31d0055a4e0410872d8 2003-04-16T19:28:13Z John Baldwin jhb@FreeBSD.org 2003-04-16T19:28:13Z urn:sha1:f36a83deffd9b84c67243edf775a01f7bf66142b wrong place. 2003-03-03T09:17:12Z Dag-Erling Smørgrav des@FreeBSD.org 2003-03-03T09:17:12Z urn:sha1:1d062e2be87c5ea127eb4e06199c83c86ae412f7