[Bug 283163] kill -SIG -1 does not work any more for host - which leads to inconsistent reboot

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

            Bug ID: 283163
           Summary: kill -SIG -1 does not work any more for host - which
                    leads to inconsistent reboot
           Product: Base System
           Version: 14.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: vova@fbsd.ru

Problem - I can't send signal to all process in systems:

# kill -15 -1
-1: No such process

# truss kill -15 -1
...
kill(-1,SIGTERM)     ERR#3 'No such process'

Looks like it was broken in 
https://reviews.freebsd.org/D34522
https://cgit.freebsd.org/src/commit/sys/kern/kern_sig.c?h=stable/14&id=69413598d2660054e29cac9454fe18c08e3bf36d


Can be easily spot during reboot with serial console - a number of processes
are get killed with SIGSEGV because the was not killed by reboot which sends -1
signal

---
# shutdown -r
...

Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 0 0 0 0 0 0 0 0 0 done
All buffers synced.
pid 25340 (sshd), jid 0, uid 502: exited on signal 11 (no core dump - bad
address)
pid 25338 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad
address)
pid 25567 (tcsh), jid 0, uid 502: exited on signal 11 (no core dump - other
error)
pid 25355 (tcsh), jid 0, uid 0: exited on signal 11 (no core dump - too large)
pid 25566 (sshd), jid 0, uid 502: exited on signal 11 (no core dump - bad
address)
pid 25564 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad
address)
pid 25353 (sudo), jid 0, uid 0: exited on signal 11 (no core dump - bad
address)
pid 25341 (tcsh), jid 0, uid 502: exited on signal 11 (no core dump - other
error)
pid 25354 (sudo), jid 0, uid 0: exited on signal 11 (no core dump - bad
address)
Uptime: 1h21m57s
uftdi0: detached
uhub0: detached
---

issue was discussed at
https://lists.freebsd.org/archives/freebsd-current/2024-July/006124.html
but outcome was invalid

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