lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 6 Jun 2019 13:05:22 +0200
From:   Oleg Nesterov <>
To:     David Laight <David.Laight@...LAB.COM>
Cc:     'Linus Torvalds' <>,
        Andrew Morton <>,
        Deepa Dinamani <>,
        Linux List Kernel Mailing <>,
        Arnd Bergmann <>,
        Davidlohr Bueso <>, Jens Axboe <>,
        Davidlohr Bueso <>,
        "" <>, Jason Baron <>,
        linux-fsdevel <>,
        "" <>,
        "" <>,
        Thomas Gleixner <>,
        stable <>,
        Al Viro <>,
        "Eric W. Biederman" <>
Subject: Re: [PATCH -mm 0/1] signal: simplify

On 06/06, David Laight wrote:
> If a signal handler is called, I presume that the trampoline
> calls back into the kernel to get further handlers called
> and to finally restore the original signal mask?

See sigmask_to_save(), this is what the kernel records in uc.uc_sigmask
before the signal handler runs, after that current->saved_sigmask has no

When signal handler returns it does sys_rt_sigreturn() which restores
the original mask saved in uc_sigmask.

> What happens if a signal handler calls something that
> would normally write to current->saved_sigmask?

See above.


Powered by blists - more mailing lists