From owner-freebsd-bugs@freebsd.org Fri Dec 29 22:58:45 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC4F0EB4D9E for ; Fri, 29 Dec 2017 22:58:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 AA9187FC14 for ; Fri, 29 Dec 2017 22:58:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBTMwhow033058 for ; Fri, 29 Dec 2017 22:58:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224479] kernel panic in reboot+swapoff sys call Date: Fri, 29 Dec 2017 22:58:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Dec 2017 22:58:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224479 --- Comment #24 from Mark Millard --- (In reply to Andriy Gapon from comment #23) [Ignore if you care not for my history and opinion for swapfile usage vs. partition usage.] I will note that when I ran into the deadlock problems from using a swapfile instead of a partition, it was not obvious at the time that swapspace handling was involved at all: it was also first use of a platform as well. I was not lucky to have changed just one thing to know to revert it. For all I knew the type of platform might have been having problems in general. It was a pain to figure out that swapfile use was what I could avoid using in order to avoid the hangups that were happening. To me the discovery seemed to mean that FreeBSD violated a variation on the principle of least astonishment (but not tied to changes to historical behavior). (Having a partition with UFS and only one user-file, the swapfile, might avoid some of the issues. I had done this earlier [by an accidental choice] on powerpc64 and powerpc and had not seen any problems. This contributed to my not challenging the swapfile use earlier in trying to isolate contributions to the hangups: I did not then realize that I'd done something possibly special in that earlier use.) --=20 You are receiving this mail because: You are the assignee for the bug.=