Date: Wed, 29 Dec 2021 11:10:45 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260793] 'swapon -a' can crash the system Message-ID: <bug-260793-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260793 Bug ID: 260793 Summary: 'swapon -a' can crash the system Product: Base System Version: 12.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: pmc@citylink.dinoex.sub.org Reproduce:=20 ---------- 1. Have some early and late swapspaces configured and decently filled alrea= dy. 2. With paging not yet exhausted, add another *late* swapspace into fstab. 3. Run "swapon -a". This should not do anything, because the old swapspaces are already active,= and the new one is configured as "late", and a mere "swapon -a" would not activ= ate it. Error: ------ kernel: pid 12296 (daemon), jid 5, uid 5100: exited on signal 10 (core dump= ed) kernel: pid 17717 (ruby27), jid 5, uid 5100: exited on signal 6 (core dumpe= d) kernel: pid 14938 (daemon), jid 10, uid 5100: exited on signal 10 (core dum= ped) kernel: pid 19184 (ruby27), jid 10, uid 5100: exited on signal 11 (core dum= ped) kernel: pid 19182 (ruby27), jid 10, uid 5100: exited on signal 10 (core dum= ped) [etc. etc. lots of them] And subsequent kernel crash. (It might appear that the processes coredumping are those that are fully swapped out, but this is unconfirmed). I did not find time to analyze this in-depth; it happened twice, it is obvi= ous that 'swapon -a' does mangle something seriousely, so I just don't use it anymore except during bringup. --=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-260793-227>