src-test2/sys/compat/svr4, branch stable/10

MF11 r331330: Fix kernel memory disclosure in svr4_sys_getdents64

2018-03-29T22:31:14Z

svr4_sys_getdents64() copies a dirent structure to userland. When calculating the record length for any given dirent entry alignment is performed. However, the aligned bytes are not cleared, this will trigger an info leak. Reported by: Ilja Van Sprundel Security: Kernel memory disclosure (801) Sponsored by: The FreeBSD Foundation

MFC r281436 (by mjg@):

2017-07-15T17:25:40Z

fd: remove filedesc argument from fdclose Just accept a thread instead. This makes it consistent with fdalloc. No functional changes.

MFC 313564:

2017-05-10T23:09:17Z

Drop the "created from" line from files generated by makesyscalls.sh. This information is less useful when the generated files are included in source control along with the source. If needed it can be reconstructed from the $FreeBSD$ tag in the generated file. Removing this information from the generated output permits committing the generated files along with the change to the system call master list without having inconsistent metadata in the generated files. Regenerate the affected files along with the MFC.

MFC r303464 (by brooks@):

2017-03-11T08:40:59Z

Don't create pointless backups of generated files in "make sysent". Any sensible workflow will include a revision control system from which to restore the old files if required. In normal usage, developers just have to clean up the mess.

MFC r298519:

2016-05-07T08:30:21Z

Fix streams and svr4 module dependency. Both modules are complaining about undefined symbol svr4_delete_socket which was moved from streams to the svr4 module in r160558 that created a two-way dependency between them. MFC r298520: Allow to build svr4 module with SYSV support separatelly from the kernel build. PR: 208464 Reported by: Kristoffer Eriksson

MFC r293613:

2016-01-16T07:56:49Z

Implement vsyscall hack. Prior to 2.13 glibc uses vsyscall instead of vdso. An upcoming linux_base-c6 needs it.

MFC r283382:

2016-01-09T14:53:08Z

In preparation for switching linuxulator to the use the native 1:1 threads add a hook for cleaning thread resources before the thread die.

To facillitate an upcoming Linuxulator merging partially

2016-01-09T14:08:10Z

MFC r275121 (by kib). Only merge the syntax changes from r275121, PROC_*LOCK() macros still lock the same proc spinlock. The process spin lock currently has the following distinct uses: - Threads lifetime cycle, in particular, counting of the threads in the process, and interlocking with process mutex and thread lock. The main reason of this is that turnstile locks are after thread locks, so you e.g. cannot unlock blockable mutex (think process mutex) while owning thread lock. - Virtual and profiling itimers, since the timers activation is done from the clock interrupt context. Replace the p_slock by p_itimmtx and PROC_ITIMLOCK(). - Profiling code (profil(2)), for similar reason. Replace the p_slock by p_profmtx and PROC_PROFLOCK(). - Resource usage accounting. Need for the spinlock there is subtle, my understanding is that spinlock blocks context switching for the current thread, which prevents td_runtime and similar fields from changing (updates are done at the mi_switch()). Replace the p_slock by p_statmtx and PROC_STATLOCK(). Discussed with: kib

MFC r282708:

2015-05-24T07:32:02Z

On exec, single-threading must be enforced before arguments space is allocated from exec_map.

Merge r263233 from HEAD to stable/10:

2015-03-19T13:37:36Z

Update kernel inclusions of capability.h to use capsicum.h instead; some further refinement is required as some device drivers intended to be portable over FreeBSD versions rely on __FreeBSD_version to decide whether to include capability.h. Sponsored by: Google, Inc.