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 14:41:03 +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:
> Some of this code is hard to grep through :-)

I'd suggest to simply read the kernel code once and memorise it, after
that you will not need to use grep.

> > When signal handler returns it does sys_rt_sigreturn() which restores
> > the original mask saved in uc_sigmask.
> Does that mean that if 2 signals interrupt epoll_wait() only
> one of the signal handlers is run?

I'll assume that both signals were blocked before syscall and temporary
unblocked by pselect.

Quite contrary, they both will be delivered exactly because original mask
won't be restored until the 1st handler returns.

Unless, of course, the sigaction->sa_mask of the 1st signal blocks another

Didn't I say you do not read my emails? I have already explained this to
you in this thread ;)


Powered by blists - more mailing lists