User Details
- User Since
- May 16 2014, 7:35 PM (637 w, 4 d)
Today
Handle KEY_SETSECASIDX() and KEY_SETSECSPIDX().
Yesterday
List the busy action in the comment about unlocking.
If this is a solution, then IMO it should be activated by default. How would user know to tweak this knob if SR-IOV fails?
I do not see how this could be an option. Either there is no (bad) impact on the native umtxes, and then we should just change the constant, perhaps adding a comment explaining its origin and reasoning behind. Or there is the impact, but then you could check that the curproc ABI is linux, and use the proposed constant for Linux processes.
Sun, Aug 2
Fore
segments
mention 'non-synthetic' for filesystems
Add comment.
Do not unconditionally disable recursion for coveredvnode on error.
What are the hypothetical KBI incompatibilities caused by the FRED commit?
The patch requires a lot of work. It is not complicated, but quite time consuming. Also, it requires access to dual-bool the machine with Linux and FreeBSD, to compare the outcome on the same system.
Sat, Aug 1
This patch adds a capability for ptrace, and allows to do ptrace(req, procdesc, addr, data) instead of ptrace(req, pid, addr, data).
Fri, Jul 31
I wonder if we should start provide the definitive list of MI aromics in atomic(9).
I handled the SIGCHLD delivery check in the destructor somewhat rude, but the tests are not structured to make it easy to handle properly.
Also I did not tried that under Linux, I think it is not needed.
Thu, Jul 30
More tabs.
Use tabs after .if/.err
tabs not spaces
clang <= 18.
.err for non-ax.
More tests updates
I do not object, but I also note that rtld trusts the format of the objects to be correct. There is a lot of missed bounds checks.
Wed, Jul 29
Clear PZOMBIEREF_PROCDESC when the last procdesc reference is gone.
Man page editing.
The changes required to the test suite are very illustrative.
