From owner-freebsd-bugs@freebsd.org  Wed Dec 27 20:20:35 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 E5BE3EAAEA3
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 27 Dec 2017 20:20:35 +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 D4781764B1
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 Dec 2017 20:20:35 +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 vBRKKZZH070068
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 Dec 2017 20:20:35 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: Wed, 27 Dec 2017 20:20:35 +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: <bug-224479-8-ADzl90Nj9L@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224479-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-224479-8@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Dec 2017 20:20:36 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224479

--- Comment #13 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Wolfram Schneider from comment #12)

Does the problem happen for:

shutdown -r now

instead of reboot?

I ask because the man page for reboot says that
reboot does not cleanly shut down all processes,
recommending the use of shutdown instead:

 Normally, the shutdown(8) utility is used when the system needs to be
     halted or restarted, giving users advance warning of their impending d=
oom
     and cleanly terminating specific programs.

So, reboot is documented to be more likely to have
race conditions.

Side note:

Going the other direction, given what is known
about file-system swapspaces (i.e., vnode-backed),
I'm not sure why they are allowed by default
instead of needing support to be explicitly
enabled. (The enabling indicating that one is
supposed to understand the issues involved in
their use.)

--=20
You are receiving this mail because:
You are the assignee for the bug.=