Also, do you have any particular cases or example of application where you want to use it?

I think this behavior should be documented in the man pages (capsicum/wait), as it isn't obvious.

Hello Alexander,

In D43638#995136, @imp wrote:

Seems reasonable to me.
Who will be using this?

What about the header fields we have discussed?

Thanks!

I've updated all of them now. But do you think that this is too pedantic

No, I think that this is a fair statement. I have a couple of questions about this and the libnv.

LGTM, thank you for working on this.

Hello Jake,

Ah, ok I thought it was printed by default.
Then I don't think I have any complaints through the idea.

If I understand correctly, for application like:

localtime();
open();
cap_enter()
openat()

To summarize the patch very briefly, this lets you ktrace an application that does not run in capability mode, and ktrace will log all events which would have triggered a Capsicum violation.

Yea, I guess you are right when copy_file_range has offset NULLed it behaves more like read/write then pread/pwrite.

@kib

Yes, thats make sense. Thank you.

kib@ thank you. Moved to libuitl.

Move to libuitl

Update description.

Add more context to the file.

Sorry for the delay.

@imp Have you had a chance to look into this?

Use sizeof.

Fix description

LGTM.
Nice catch.

I don't mind also moving them simply to /lib.

The idea for a separate directory was that we would have many libcasper helpers, and the /lib will get crowdy.
The Casper libraries are quite limited in number so I'm not sure if it's worth it to keep a separate directory here.

Hym, sorry, last time it showed me that you almost added the whole sys/kern/kern_procctl.c. I guess it was some glitch in phabricator.