[lkml]   [2012]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 20/40] mn10300: Use set_current_blocked() and block_sigmask()
    Oleg Nesterov <> wrote:

    > No, only current can change ->blocked. This is even documented in
    > sigprocmask(). And more, the only correct way to change ->blocked
    > is set_current_blocked(). OK, with a couple of "I know what I am
    > doing" exceptions in kernel/signal.c.

    I was looking at force_sig_info() and derivatives. Is that what you refer to?

    If so, is it worth providing a force_sig_info_current(),
    force_sigsegv_current() and force_sig_current() to make things clearer to grep
    for, I wonder?


     \ /
      Last update: 2012-02-14 19:15    [W:0.018 / U:60.940 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site