src/lib/libkvm, branch release/13.1.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F13.1.02022-02-17T01:18:32Zlibkvm: fix kvm_walk_pages2022-02-17T01:18:32ZBora Özarslanborako.ozarslan@gmail.com2021-11-25T19:09:26Zurn:sha1:503ac069aa4cabd8fb3aeaec705c5c926e39d452
Correct bitmap operations in _kvm_bitmap_next.
Reviewed by: jhb
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D19183
(cherry picked from commit 08055452cbf24a3cea48cb4f665bab78d89b7a39)
libkvm: Fix build after removal of p_tracevp2021-06-13T01:22:33ZKonstantin Belousovkib@FreeBSD.org2021-05-22T12:43:57Zurn:sha1:cf852eda68a8f66c9f7ce0f0b9cecd1d58915685
(cherry picked from commit e67ef6ce667d42a235a70914159048e10039145d)
libkvm: Plug couple of memory leaks and check possible calloc(3) failure2021-03-06T19:32:51ZJung-uk Kimjkim@FreeBSD.org2021-03-03T23:10:00Zurn:sha1:eda8f0575dda15346116d3be84b205c51c83e20b
First, r204494 introduced dpcpu_off in struct __kvm and it was allocated
from _kvm_dpcpu_init() but it was not free(3)'ed from kvm_close(3).
Second, r291406 introduced kvm_nlist2(3) and converted kvm_nlist(3) to
use the new function but it did not free the temporary buffer.
Also, check possible calloc(3) failure while I am in the neighborhood.
Differential Revision: https://reviews.freebsd.org/D29019
(cherry picked from commit 645eaa2ccaed6eea801d07d6a092974fc1713896)
(cherry picked from commit 483c6da3a20b2064cd655f7cb19e6b98dee677ff)
jobc: rework detection of orphaned groups.2021-01-10T02:41:20ZKonstantin Belousovkib@FreeBSD.org2020-12-29T00:41:56Zurn:sha1:5844bd058aed6f3d0c8cbbddd6aa95993ece0189
Instead of trying to maintain pg_jobc counter on each process group
update (and sometimes before), just calculate the counter when needed.
Still, for the benefit of the signal delivery code, explicitly mark
orphaned groups as such with the new process group flag.
This way we prevent bugs in the corner cases where updates to the counter
were missed due to complicated configuration of p_pptr/p_opptr/real_parent
(debugger).
Since we need to iterate over all children of the process on exit, this
change mostly affects the process group entry and leave, where we need
to iterate all process group members to detect orpaned status.
(For MFC, keep pg_jobc around but unused).
Reported by: jhb
Reviewed by: jilles
Tested by: pho
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D27871
Always use 64-bit physical addresses for dump_avail[] in minidumps2020-12-03T17:12:31ZMark Johnstonmarkj@FreeBSD.org2020-12-03T17:12:31Zurn:sha1:b957b185946ed5ad96436b50bb118db8c1a24ded
As of r365978, minidumps include a copy of dump_avail[]. This is an
array of vm_paddr_t ranges. libkvm walks the array assuming that
sizeof(vm_paddr_t) is equal to the platform "word size", but that's not
correct on some platforms. For instance, i386 uses a 64-bit vm_paddr_t.
Fix the problem by always dumping 64-bit addresses. On platforms where
vm_paddr_t is 32 bits wide, namely arm and mips (sometimes), translate
dump_avail[] to an array of uint64_t ranges. With this change, libkvm
no longer needs to maintain a notion of the target word size, so get rid
of it.
This is a no-op on platforms where sizeof(vm_paddr_t) == 8.
Reviewed by: alc, kib
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D27082
Split out cwd/root/jail, cmask state from filedesc table2020-11-17T21:14:13ZConrad Meyercem@FreeBSD.org2020-11-17T21:14:13Zurn:sha1:85078b8573332c2c83a79adea8a61b519fb3b6af
No functional change intended.
Tracking these structures separately for each proc enables future work to
correctly emulate clone(2) in linux(4).
__FreeBSD_version is bumped (to 1300130) for consumption by, e.g., lsof.
Reviewed by: kib
Discussed with: markj, mjg
Differential Revision: https://reviews.freebsd.org/D27037
libkvm: catch up with pre-subtracated per-cpu addresses2020-10-06T02:57:37ZMateusz Guzikmjg@FreeBSD.org2020-10-06T02:57:37Zurn:sha1:f165a1df9a8fb7bd57780b433cfb4c2cb3d1d9f4
Only concerns amd64.
Reported by: imp
Do a sweep and remove most WARNS=6 settings2020-10-01T01:10:51ZKyle Evanskevans@FreeBSD.org2020-10-01T01:10:51Zurn:sha1:7cc42f6d25ef2e19059d088fa7d4853fe9afefb5
Repeating the default WARNS here makes it slightly more difficult to
experiment with default WARNS changes, e.g. if we did something absolutely
bananas and introduced a WARNS=7 and wanted to try lifting the default to
that.
Drop most of them; there is one in the blake2 kernel module, but I suspect
it should be dropped -- the default WARNS in the rest of the build doesn't
currently apply to kernel modules, and I haven't put too much thought into
whether it makes sense to make it so.
[PowerPC64LE] libkvm powerpc64le support.2020-09-23T02:11:24ZBrandon Bergrenbdragon@FreeBSD.org2020-09-23T02:11:24Zurn:sha1:f4eb39ba6bc914e380edb6088041d0deb3fe1b13
* Add missing _kvm16toh() function.
* Teach libkvm about powerpc64le.
Sponsored by: Tag1 Consulting, Inc.
Sparsify the vm_page_dump bitmap2020-09-21T22:21:59ZD Scott Phillipsscottph@FreeBSD.org2020-09-21T22:21:59Zurn:sha1:00e6614750deca2457373aecd5bfa7aebbde3865
On Ampere Altra systems, the sparse population of RAM within the
physical address space causes the vm_page_dump bitmap to be much
larger than necessary, increasing the size from ~8 Mib to > 2 Gib
(and overflowing `int` for the size).
Changing the page dump bitmap also changes the minidump file
format, so changes are also necessary in libkvm.
Reviewed by: jhb
Approved by: scottl (implicit)
MFC after: 1 week
Sponsored by: Ampere Computing, Inc.
Differential Revision: https://reviews.freebsd.org/D26131