Date: Thu, 28 Dec 2017 17:36:32 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224479] kernel panic in reboot+swapoff sys call Message-ID: <bug-224479-8-u8PMTjxXiN@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224479 --- Comment #18 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Andriy Gapon from comment #15) This is perhaps going too far on the silly fest. Andrey, you do understand VFS, so I am quite frustrated. 1. If the vnode carriers some database, should kernel stop the database on = the basis that otherwise user data might be corrupted ? Should kernel print (Abort, Retry, Ignore ?) 2.If force unmount is not allowed because there is the swap on a file, would the next request be to add really-force option which causes unmount to proc= eed even in this case. 3. You agree on your own that io to reclaimed vnode is not possible. May b= e we should not reclaim such vnode, but then add VOP_RECLAIMFORREAL. It is very clear situation, system was directed to change its configuration= in a way which makes the continuation of the operations sometimes problematic, sometimes not. Why people consider it is reasonable to either deny the reconfiguration or to deny and have kernel to spit the whole man page on the console as the additional punishment, is beyond me. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224479-8-u8PMTjxXiN>