Date: Fri, 29 Dec 2017 22:58:44 +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-9CZttrR97C@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224479 --- Comment #24 from Mark Millard <markmi@dsl-only.net> --- (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.) -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224479-8-9CZttrR97C>
