From owner-freebsd-current@freebsd.org Mon Feb 12 08:59:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D7D9F0457D for ; Mon, 12 Feb 2018 08:59:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7282D87D11 for ; Mon, 12 Feb 2018 08:59:07 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w1C8wqPe047235 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 12 Feb 2018 10:58:55 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w1C8wqPe047235 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w1C8wqpc047234; Mon, 12 Feb 2018 10:58:52 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 12 Feb 2018 10:58:52 +0200 From: Konstantin Belousov To: Ryan Stone Cc: FreeBSD Current Subject: Re: Panic in prison_alloc() on boot Message-ID: <20180212085852.GA94212@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 08:59:08 -0000 On Sun, Feb 11, 2018 at 11:50:43PM -0500, Ryan Stone wrote: > I'm getting a persistent panic on boot in prison_allow(). The first > case that I hit is this: > > Fatal trap 12: page fault while in kernel mode > cpuid = 10; apic id = 22 > fault virtual address = 0x30 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80ab9674 > stack pointer = 0x28:0xfffffe00f8bb16f0 > frame pointer = 0x28:0xfffffe00f8bb16f0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 90 (mount_nullfs) > [ thread pid 90 tid 100913 ] > Stopped at prison_allow+0x4: movq ll+0xf(%rdi),%rax > db> bt > Tracing pid 90 tid 100913 td 0xfffff801a5aab000 > prison_allow() at prison_allow+0x4/frame 0xfffffe00f8bb16f0 Can you get the core dump and look at the arguments ? It is most likely cred->cr_prison which is NULL. > nullfs_mount() at nullfs_mount+0x31/frame 0xfffffe00f8bb1830 > vfs_donmount() at vfs_donmount+0x1415/frame 0xfffffe00f8bb1a80 > sys_nmount() at sys_nmount+0x72/frame 0xfffffe00f8bb1ac0 > amd64_syscall() at amd64_syscall+0xa48/frame 0xfffffe00f8bb1bf0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0x7fffffffecb0 > > However if I comment out my nullfs mounts in /etc/fstab, I just get a > panic in prison_allow() called from elsewhere. > > I've seen this panic with r328936 (Feb 6), r329091 (Feb 9) and r329142 (Feb 11) > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"