Date: Tue, 11 Jan 2022 19:49:18 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260793 --- Comment #5 from Peter Much <firstname.lastname@example.org> --- Mark, there seems to be a logical flaw in here: You say we would be safe if the swap would be opened in write-exclusive mode. And You say, this cannot be done because of 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 activated 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 savecore(8) access a swapspace that has been trimonce'd right before? (The swapon(8) manpage does already say that this wouldn't work.) -- You are receiving this mail because: You are the assignee for the bug.