mdmfs fails for first time with md (Was: Regression: ALPHA3 can not properly init diskless / nanobsd system (mdmfs or mknewfs or md is broken?))
Hello Lev, Tuesday, September 4, 2018, 2:25:21 AM, you wrote: > arc4random: no preloaded entropy cache > arc4random: no preloaded entropy cache > random: read_random_uio unblock wait > random: read_random_uio unblock wait > random: unblocking device. > mdmfs: mount exited with error code 1 > cp: /etc/periodic/monthly/999.local and > /conf/base/etc/periodic/monthly/999.local are identical (not copied). > It fails for first time, but works after that (for /tmp and /var). > My kernel doesn't have TMPFS compiled in. Looks like it is hardware-depended. It works on Atom D2500-based system and 100% fails on Celeron J3160 based one. How could I debug this? -- Best regards, Levmailto:l...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression: ALPHA3 can not properly init diskless / nanobsd system (mdmfs or mknewfs or md is broken?)
Hello Lev, Saturday, September 1, 2018, 2:39:12 AM, you wrote: > I have NanoBSD system built from and it works. It creates THREE memory > filesystems, as needed: > % mount | grep /dev/md > /dev/md0 on /etc (ufs, local) > /dev/md1 on /var (ufs, local) > /dev/md2 on /var/tmp (ufs, local) > % > But same system built from ALPHA3 sources (r338399 to be exact) doesn't > create /etc in-memory overlay, and can not copy SSHD keys and create > host.conf. After that sshd could not start. > New version doesn't properly create overlay for /etc: > % mount | grep /dev/md > /dev/md1 on /var (ufs, local) > /dev/md2 on /var/tmp (ufs, local) > % I've get log from boot, but it is not very informative: arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache random: read_random_uio unblock wait random: read_random_uio unblock wait random: unblocking device. mdmfs: mount exited with error code 1 cp: /etc/periodic/monthly/999.local and /conf/base/etc/periodic/monthly/999.local are identical (not copied). It fails for first time, but works after that (for /tmp and /var). My kernel doesn't have TMPFS compiled in. -- Best regards, Levmailto:l...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD -CURRENT on AMD Ryzen5
Testing out various BSD's with a Huawei Matebook D, and FreeBSD -CURRENT is failing to boot from an installer image. No serial console, so unable to grab full boot output, any other info or boot flags that would help would be awesome. https://i.imgur.com/WAqwbza.jpg, shows where boot process hangs, and fails to move past. Thanks ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: redzone catching a buffer overflow in swapoff_one
Shawn Webb shawn.webb at hardenedbsd.org wrote on Mon Sep 3 17:41:17 UTC 2018 : > I'm unsure whether this is a false positive or true positive, but it > looks like there may be a buffer overflow in swapoff_one: > > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] REDZONE: Buffer overflow > detected. 16 bytes corrupted after 0xfe1fe0023248 (2237000 bytes > allocated). > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] Allocation backtrace: > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #0 0x80e188e1 at > redzone_setup+0xe1 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #1 0x80ac8007 at > malloc+0x1d7 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #2 0x80b1f449 at > blist_create+0x99 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #3 0x80e1daa7 at > swaponsomething+0xe7 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #4 0x80e1c233 at > sys_swapon+0x413 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #5 0x80fc0e5e at > amd64_syscall+0x29e > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #6 0x80f9dc9d at > fast_syscall_common+0x101 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] Free backtrace: > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #0 0x80e18c28 at > redzone_check+0x2f8 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #1 0x80ac85af at > free_dbg+0x5f > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #2 0x80ac84aa at > free+0x1a > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #3 0x80e1cae5 at > swapoff_one+0x675 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #4 0x80e1cc57 at > swapoff_all+0xd7 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #5 0x80b9991a at > bufshutdown+0x2ca > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #6 0x80aec36e at > kern_reboot+0x21e > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #7 0x80aec0f9 at > sys_reboot+0x3a9 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #8 0x80fc0e5e at > amd64_syscall+0x29e > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #9 0x80f9dc9d at > fast_syscall_common+0x101 See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231116 for "Out of bounds memory access in blist_create()" with a Mark Johnston patch in Comment #2. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: redzone catching a buffer overflow in swapoff_one
On Mon, Sep 03, 2018 at 01:40:16PM -0400, Shawn Webb wrote: > I'm unsure whether this is a false positive or true positive, but it > looks like there may be a buffer overflow in swapoff_one: > > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] REDZONE: Buffer overflow > detected. 16 bytes corrupted after 0xfe1fe0023248 (2237000 bytes > allocated). > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] Allocation backtrace: > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #0 0x80e188e1 at > redzone_setup+0xe1 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #1 0x80ac8007 at > malloc+0x1d7 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #2 0x80b1f449 at > blist_create+0x99 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #3 0x80e1daa7 at > swaponsomething+0xe7 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #4 0x80e1c233 at > sys_swapon+0x413 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #5 0x80fc0e5e at > amd64_syscall+0x29e > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #6 0x80f9dc9d at > fast_syscall_common+0x101 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] Free backtrace: > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #0 0x80e18c28 at > redzone_check+0x2f8 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #1 0x80ac85af at > free_dbg+0x5f > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #2 0x80ac84aa at > free+0x1a > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #3 0x80e1cae5 at > swapoff_one+0x675 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #4 0x80e1cc57 at > swapoff_all+0xd7 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #5 0x80b9991a at > bufshutdown+0x2ca > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #6 0x80aec36e at > kern_reboot+0x21e > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #7 0x80aec0f9 at > sys_reboot+0x3a9 > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #8 0x80fc0e5e at > amd64_syscall+0x29e > Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #9 0x80f9dc9d at > fast_syscall_common+0x101 > > Of course, I'm running HardenedBSD 12-CURRENT/amd64. I've synced with > FreeBSD at this commit: > https://github.com/freebsd/freebsd/commit/2f2449cc1cdfc19ae34b2317e792af489418a01a > > So my src tree is at this commit: > https://github.com/HardenedBSD/hardenedBSD/commit/98f90fadab000b818a731be4650ac1a47144501c > > I've not yet studied the swap pager's code and plan to start learning > it soon. See PR 231116. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
redzone catching a buffer overflow in swapoff_one
I'm unsure whether this is a false positive or true positive, but it looks like there may be a buffer overflow in swapoff_one: Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] REDZONE: Buffer overflow detected. 16 bytes corrupted after 0xfe1fe0023248 (2237000 bytes allocated). Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] Allocation backtrace: Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #0 0x80e188e1 at redzone_setup+0xe1 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #1 0x80ac8007 at malloc+0x1d7 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #2 0x80b1f449 at blist_create+0x99 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #3 0x80e1daa7 at swaponsomething+0xe7 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #4 0x80e1c233 at sys_swapon+0x413 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #5 0x80fc0e5e at amd64_syscall+0x29e Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #6 0x80f9dc9d at fast_syscall_common+0x101 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] Free backtrace: Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #0 0x80e18c28 at redzone_check+0x2f8 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #1 0x80ac85af at free_dbg+0x5f Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #2 0x80ac84aa at free+0x1a Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #3 0x80e1cae5 at swapoff_one+0x675 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #4 0x80e1cc57 at swapoff_all+0xd7 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #5 0x80b9991a at bufshutdown+0x2ca Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #6 0x80aec36e at kern_reboot+0x21e Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #7 0x80aec0f9 at sys_reboot+0x3a9 Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #8 0x80fc0e5e at amd64_syscall+0x29e Sep 3 13:13:13 hbsd-dev-laptop kernel: [619] #9 0x80f9dc9d at fast_syscall_common+0x101 Of course, I'm running HardenedBSD 12-CURRENT/amd64. I've synced with FreeBSD at this commit: https://github.com/freebsd/freebsd/commit/2f2449cc1cdfc19ae34b2317e792af489418a01a So my src tree is at this commit: https://github.com/HardenedBSD/hardenedBSD/commit/98f90fadab000b818a731be4650ac1a47144501c I've not yet studied the swap pager's code and plan to start learning it soon. Thanks, -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal:+1 443-546-8752 Tor+XMPP+OTR:latt...@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature
