[Bug 224479] kernel panic in reboot+swapoff sys call

[bugzilla-noreply at freebsd.org]

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

--- Comment #18 from Konstantin Belousov <kib at 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 proceed
even in this case.
3. You agree on your own that io to reclaimed vnode is not possible.  May be 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.

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