From owner-freebsd-bugs@freebsd.org  Tue Dec 26 21:12:43 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 BCC83E82FA9
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 26 Dec 2017 21:12:43 +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 A87726789E
 for <freebsd-bugs@FreeBSD.org>; Tue, 26 Dec 2017 21:12:43 +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 vBQLCgb6003219
 for <freebsd-bugs@FreeBSD.org>; Tue, 26 Dec 2017 21:12:43 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: Tue, 26 Dec 2017 21:12:42 +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: kib@FreeBSD.org
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-zHJ4S82OsR@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: Tue, 26 Dec 2017 21:12:43 -0000

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

--- Comment #11 from Konstantin Belousov <kib@FreeBSD.org> ---
I do not quite understand what a cause for the complain is.  If the system
cannot get the swapped out page data on swapoff, this means that the data is
corrupted.  Preventing further user data corruption by panicing is a normal
reaction.

In the case of the swap file on the unmounted filesystem, this is expected =
mode
of failure.  Unmount reclaims the vnode, making all io to fail, putting the
system into situation described in the previous paragraph.

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