> Something doesn't feel right.
>
> db_kill_cmd finds a process, called p, then kills it. In your new diff
> calling sigexit, take note of the comment at the top:
>
> * Force the current process to exit with the specified signal, dumping core
>
> current process? Doesn't look like it, it
On 16/09/20(Wed) 02:08, Theo de Raadt wrote:
> Something doesn't feel right.
>
> db_kill_cmd finds a process, called p, then kills it. In your new diff
> calling sigexit, take note of the comment at the top:
>
> * Force the current process to exit with the specified signal, dumping core
>
>
Something doesn't feel right.
db_kill_cmd finds a process, called p, then kills it. In your new diff
calling sigexit, take note of the comment at the top:
* Force the current process to exit with the specified signal, dumping core
current process? Doesn't look like it, it looks like it kills
On 16/09/20(Wed) 06:09, Miod Vallat wrote:
>
> > Diff below introduces an helper for sending an uncatchable SIGABRT and
> > annotate that `p_siglist' and `p_sigmask' are updated using atomic
> > operations.
>
> Why not use sigexit(p, SIGABRT); for that purpose?
That's a better solution indeed.
> Diff below introduces an helper for sending an uncatchable SIGABRT and
> annotate that `p_siglist' and `p_sigmask' are updated using atomic
> operations.
Why not use sigexit(p, SIGABRT); for that purpose?
On Tue, Sep 15, 2020 at 12:52:40PM +0200, Martin Pieuchot wrote:
> Diff below introduces an helper for sending an uncatchable SIGABRT and
> annotate that `p_siglist' and `p_sigmask' are updated using atomic
> operations.
>
> As a result setsigvec() becomes local to kern/kern_sig.c.
>
> Note that
Diff below introduces an helper for sending an uncatchable SIGABRT and
annotate that `p_siglist' and `p_sigmask' are updated using atomic
operations.
As a result setsigvec() becomes local to kern/kern_sig.c.
Note that other places in the kernel use sigexit(p, SIGABRT) for the
same purpose and
