In D37013#975931, @cy wrote:

LGTM.

Prior to commit, can I please have your full name and email address so that I can fill in the --author field?

The subject line and summary have been adjusted to make for a good commit log message.

In D37013#975891, @cy wrote:

===> Checking for items in STAGEDIR missing from pkg-plist
Error: Orphaned: share/info/ctf-spec.info
Error: Orphaned: share/info/sframe-spec.info
===> Checking for items in pkg-plist which are not in STAGEDIR
===> Error: Plist issues found.
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/binutils

fix unwanted info files when INFO disabled

In D37013#975828, @cy wrote:

/tmp/D37013.diff:50: space before tab in indent.

	$(MAKE) $(AM_MAKEFLAGS) check-recursive

Rebased the diff to new port version (2.37 -> 2.40)

Because of math/gmp already patched by PR 259573, removing it from my diff.
Also rebased math/mpfr patch to the new version (but it remains nearly the same).

@glebius ?

added math/mpfr too

Please note such things:

Document the change in man pages.

In D34579#828698, @glebius wrote:

I can't see how this can be used maliciously, e.g. forcing some application outside of jail to send its SCM_RIGHTS to a jail.

with the assumption that client-allocated struct usem is 64-bit aligned

In D36272#825614, @kib wrote:

Could you please mail me git format-patch with the change, proper commit log, and author?

removed extra { }

avoid possible race when clearing _has_waiters

related: https://reviews.freebsd.org/D20772

fixed file path in diff

@trasz could you please say something about this?

Found a race between sys_exit() -> exit1() -> thread_exit() and sys_wait() -> proc_reap().
Slightly moving down PROC_SUNLOCK() in thread_exit() to protect RACCT_RT calculations from proc_reap() destroying p->p_racct.

For example it is possible to share file descriptor tables, and one of the processes may not be encumbered by the jail.

Found same function in lib/libkvm/kvm_proc.c, patch it too.

As for 64/64 divides on 32bit platform: in fact, (nearly) all 32-bit CPUs have a 32-bit tickrate (<4.2GHz), and modern compilers/libraries seems to use 64/32 math in runtime for such a case in 32-bit mode (__udivdi3 function).

I didn't done the test by myself, but this is trivial integer arithmetic.

Is it possible to find out how this was tested?

Is "firk <firk@cantconnect.ru>" the desired author for the git commit?

simplify things according to replies