Date: Sun, 27 Dec 2015 03:38:48 -0500 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: freebsd-current@freebsd.org Subject: isofs kernel panic Message-ID: <20151227083848.GA43841@mutt-hardenedbsd>
next in thread | raw e-mail | index | archive | help
--gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey All, This is from booting a new installer ISO, generated today from a very recent commit: =3D=3D=3D Begin Log =3D=3D=3D Trying to mount root from cd9660:/dev/iso9660/11_0__HBSD_AMD64_CD [ro]... lock order reversal: 1st 0xfffffe00f6222e40 bufwait (bufwait) @ /jenkins/workspace/HardenedBSD-= master-amd64/sys/vm/vm_pager.c:380 2nd 0xfffff800063785f0 isofs (isofs) @ /jenkins/workspace/HardenedBSD-mast= er-amd64/sys/kern/imgact_elf.c:883 stack backtrace: #0 0xffffffff80a7ce70 at witness_debugger+0x70 #1 0xffffffff80a7cd71 at witness_checkorder+0xe71 #2 0xffffffff80a0033b at __lockmgr_args+0xd3b #3 0xffffffff80ac2fdc at vop_stdlock+0x3c #4 0xffffffff80fc0fc0 at VOP_LOCK1_APV+0x100 #5 0xffffffff80ae397a at _vn_lock+0x9a #6 0xffffffff809c4b01 at exec_elf64_imgact+0xa91 #7 0xffffffff809e35e9 at kern_execve+0x4b9 #8 0xffffffff809e2ddc at sys_execve+0x4c #9 0xffffffff809c760a at start_init+0x26a #10 0xffffffff809eadb4 at fork_exit+0x84 #11 0xffffffff80e4e9ae at fork_trampoline+0xe userret: returning with the following locks held: exclusive lockmgr bufwait (bufwait) r =3D 0 (0xfffffe00f6222c10) locked @ /= jenkins/workspace/HardenedBSD-master-amd64/sys/vm/vm_pager.c:380 exclusive lockmgr bufwait (bufwait) r =3D 0 (0xfffffe00f6222e40) locked @ /= jenkins/workspace/HardenedBSD-master-amd64/sys/vm/vm_pager.c:380 panic: witness_warn =3D=3D=3D End Log =3D=3D=3D This is 11-CURRENT/amd64, based on HardenedBSD commit f0a4c61a2e9e2433db632d70d5764e79c5b84b7a. I booted the ISO up in bhyve using vmrun.sh. I haven't ruled out anything on HardenedBSD's side, yet, but we don't have any changes that would cause a panic'ing LOR in vm_pager.c. I'll do some more investigative work when I get some more sleep. But if anyone has any ideas, please let me know. I kinda wonder if this is related to the recent VFS changes by FreeBSD. Thanks, --=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --gKMricLos+KVdGMg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWf6OVAAoJEGqEZY9SRW7uiq0P/iv9DLCaJT/Rg5LF+elBd/GA p5JBqEzheQTRiACBAgEaKA+A6/zNK1aux+I0cyAw2WIvYeeLF6aptdaH9C6eeMjj iWEQ9/NFDL1Or5TFUn1X8Hp9spEQxcgBI9qFBISOqV5iBhgxYsCUppF3eC/TdJVW 50nkGPAJ/CMgGUnOiVvAGq+IKgzr8n/kWS+lZSAbBQ9r0OfICtBNUW80yuCDNks/ BzvBlg0LYFCaLZdx/Cu8o5+2MEUWUNSVLSkkmLnPI1PRAzdYtxCF0FxZuPMlSXG1 BFzzJhJEkFrcTbXof/IjhZl0UQyC0Fc9iXCtNS3/yRQ1jG0JFWW4WR9ll9fIeEv+ bzoyjnVrAF5DlZJU8ReGi89Nzw67BGbY3iTgPugkcaNYg/ByuNazDHK4F5yMpppN VC/G6sH7nwP2UnsOybdd+9ImLZ2S/2dQtzXMEZGvkS9/jbcxWQ8OgD7ULVvrBAD0 Zf1VeS4Ss/h35gDgTZD4op15HopIma6s+DoT3KSHnfRyAutkWZGAfeYyaUF9JbSr /7DmzbI46ugKrhNGSnCYZRAiMXMpfoPHPXj2+WgUzGEAHVAMJhPFhD9zaBABhIeX X/ucLU8xNoOwCPnOIM3cONFv4SBL3tgznZGbFTWBko9GO2wrY3lNWRaexOaKUoDS 4EeNgTexKZUw1BvxvRGl =+VP3 -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151227083848.GA43841>