Date: Tue, 11 Jan 2022 19:49:18 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260793] 'swapon -a' can crash the system Message-ID: <bug-260793-227-TPDAHunZU1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260793-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260793-227@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=3D260793 --- Comment #5 from Peter Much <pmc@citylink.dinoex.sub.org> --- Mark,=20 there seems to be a logical flaw in here: You say we would be safe if the swap would be opened in write-exclusive mod= e. And You say, this cannot be done because of=20 https://github.com/freebsd/freebsd-src/blob/main/sys/vm/swap_pager.c#L3006 which says that savecore(8) needs write access to it. Now I am wondering what business savecore(8) might have on an already activ= ated swap anyway - because I would think it's just too late then. But what I definitely don't understand: what is the point of having savecor= e(8) access a swapspace that has been trimonce'd right before? (The swapon(8) manpage does already say that this wouldn't work.) --=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-TPDAHunZU1>