[Openvpn-devel,0/5] Improve signals and avoid losing high priority ones

Message ID 20230101215109.1521549-1-selva.nair@gmail.com
Headers show
Series Improve signals and avoid losing high priority ones | expand

Message

Selva Nair Jan. 1, 2023, 9:51 p.m. UTC
From: Selva Nair <selva.nair@gmail.com>

Back to my long-forgotten signal patch -- cleaned up and rebased.
What better to do on a Jan 1st afternoon...

Commits:

1.  Preparing for better signal handling: some code refactoring
2.  Refactor signal handling in openvpn_getaddrinfo
3.  Assign and honour signal priority order
4.  Fix signal handling on Windows
5.  Improve signal handling using POSIX sigaction

Commits 1 to 4 are fairly non-intrusive and should fix trac #639 and #311
(or github #205) for most practical purposes.

Commit 5 rewrites sig.c using sigaction for proper masking of signals during
updates. May be too intrusive and too late to get well-tested for 2.6.

Comments

Selva Nair Jan. 2, 2023, 7:44 p.m. UTC | #1
Please use v2 for 4/5 and 5/5 -- sorry about the noise.

On Sun, Jan 1, 2023 at 4:51 PM <selva.nair@gmail.com> wrote:

> From: Selva Nair <selva.nair@gmail.com>
>
> Back to my long-forgotten signal patch -- cleaned up and rebased.
> What better to do on a Jan 1st afternoon...
>
> Commits:
>
> 1.  Preparing for better signal handling: some code refactoring
> 2.  Refactor signal handling in openvpn_getaddrinfo
> 3.  Assign and honour signal priority order
> 4.  Fix signal handling on Windows
> 5.  Improve signal handling using POSIX sigaction
>
> Commits 1 to 4 are fairly non-intrusive and should fix trac #639 and #311
> (or github #205) for most practical purposes.
>
> Commit 5 rewrites sig.c using sigaction for proper masking of signals
> during
> updates. May be too intrusive and too late to get well-tested for 2.6.
>