In D34184#804474, @kib wrote:I still want the answer about use of the kernel addresses for kqueue/eventfd. Generally we try to not introduce new interfaces that directly expose KVA, whatever silly the idea of KASLR is.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Jun 14 2022
Jun 14 2022
damjan.jov_gmail.com added a comment to D34184: struct kinfo_file changes needed for lsof to work using only usermode APIs.
Apr 13 2022
Apr 13 2022
damjan.jov_gmail.com added a comment to D34323: Add a kern.lockf sysctl to list the advisory byte-range locks on a specific vnode.
This is probably irrelevant now that D34756 added a more general way to retrieve advisory lock info.
damjan.jov_gmail.com added a comment to D34184: struct kinfo_file changes needed for lsof to work using only usermode APIs.
Is this still relevant?
D34756 added a more general way to retrieve advisory lock info.
Feb 22 2022
Feb 22 2022
damjan.jov_gmail.com abandoned D34090: Kernel changes needed for lsof to work using only user mode APIs.
Thank you for your feedback. New versions of this patch are at:
https://reviews.freebsd.org/D34184
https://reviews.freebsd.org/D34323
Feb 20 2022
Feb 20 2022
damjan.jov_gmail.com updated the diff for D34184: struct kinfo_file changes needed for lsof to work using only usermode APIs.
Also:
- Add a kf_eventfd_addr field to kf_eventfd and populate it.
Feb 6 2022
Feb 6 2022
Feb 2 2022
Feb 2 2022
damjan.jov_gmail.com added a comment to D34090: Kernel changes needed for lsof to work using only user mode APIs.
In D34090#771897, @emaste wrote:Kernel changes needed for lsof to work using only user mode APIs,
Can you confirm that with the set of changes here and without use of kvm, lsof's full functionality is available?
Jan 29 2022
Jan 29 2022
damjan.jov_gmail.com updated the diff for D34090: Kernel changes needed for lsof to work using only user mode APIs.
Added kf_pipe_buffer_[in/out/size] fields to kf_pipe.
Dec 6 2021
Dec 6 2021
In D33277#752192, @kib wrote:In D33277#752190, @markj wrote:Why not a sysctl-based interface, where the fd is a component of the MIB? Then info for a specific fd can be grabbed from a different process.
There is already kern.proc.filedesc, and I highly doubt that somebody needs a path for individual fd of remote process.
Sep 19 2021
Sep 19 2021
May 4 2018
May 4 2018