Re: request for testing: malloc and large allocations

2022-01-31 Thread Otto Moerbeek
On Fri, Jan 28, 2022 at 05:17:48PM +0100, Otto Moerbeek wrote: > On Fri, Jan 28, 2022 at 04:33:28PM +0100, Alexander Bluhm wrote: > > > On Sun, Jan 09, 2022 at 02:54:43PM +0100, Otto Moerbeek wrote: > > > currently malloc does cache a number of free'ed regions up to 128k in > > > size. This cache

Re: Missing UBSan libs

2022-01-31 Thread Greg Steuck
Patrick Wildt writes: > regarding the missing userpace support: Since a few clang updates ago > we import more than just the builtins of compiler-rt. This means we > should have at least some related code in our tree, even if it is not > built/complete. From the recent static analyzer mail thr

Re: in4_cksum changes, step 1

2022-01-31 Thread Miod Vallat
> The register is set to -1, all bits set, and then its upper half > is cleared. Now that the "and" has been removed, the value seems > unused. The result of the removed "and" seemed unused too. Oh, indeed, you're right, that makes things even simpler. New diff: Index: sys/arch/alpha/alpha/in_ck

fdisk: Preserve BIOS boot partition with -A

2022-01-31 Thread Visa Hankala
This patch makes fdisk -A preserve BIOS boot partition. When PolarFire SoC boots, the Hart Software Services (HSS) firmware loads HSS payload that contains U-Boot (and possibly OpenSBI) from eMMC or SD card. If there is a valid GPT header, the payload is loaded from GPT partition with type 216861

Re: in4_cksum changes, step 1

2022-01-31 Thread Visa Hankala
On Sun, Jan 30, 2022 at 06:37:39PM +, Miod Vallat wrote: > > > - sum += in_cksumdata((caddr_t) &ipov, sizeof(ipov)); > > > + sum += in_cksumdata((caddr_t) &ipov + 8, sizeof(ipov) - 8); > > > > I think this would be clearer with a comment. > > Sure, added one. > > > Please rem

Re: uvm_unmap_kill_entry(): unwire with map lock held

2022-01-31 Thread Martin Pieuchot
On 31/01/22(Mon) 10:24, Klemens Nanni wrote: > Running with my uvm assert diff showed that uvm_fault_unwire_locked() > was called without any locks held. > > This happened when I rebooted my machine: > > uvm_fault_unwire_locked() > uvm_unmap_kill_entry_withlock() > uvm_unmap_kil

uvm_unmap_kill_entry(): unwire with map lock held

2022-01-31 Thread Klemens Nanni
Running with my uvm assert diff showed that uvm_fault_unwire_locked() was called without any locks held. This happened when I rebooted my machine: uvm_fault_unwire_locked() uvm_unmap_kill_entry_withlock() uvm_unmap_kill_entry() uvm_map_teardown() uvmspace_f