# Re: \[PATCH 20/40\] mn10300: Use set\_current\_blocked() and block\_sigmask()

- From: David Howells \<dhowells@redhat.com\>
- Date: 2012-02-14 18:13:22 
- List: linux-arch
- Page: https://ratatoskr.run/linux-arch/2012/02/3822390
- Thread: https://ratatoskr.run/linux-arch/2012/02/3822231/t.md

```text
Oleg Nesterov [ref] 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?

David
```