On Fri, 2012-04-27 at 19:54 +0200, Oleg Nesterov wrote: > On 04/27, Oleg Nesterov wrote: > > > > Not only sigreturn. Just look at sigprocmask(SIG_SETMASK) callers, almost > > all should be converted to use set_current_blocked(). For example, pselect. > > which btw doesn't need sigsaved. > > > The last thing. Matt, could you please look at > > git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git ? It seems to me > > you already sent some of these changes (use set_current_blocked/block_sigmask). > > Perhaps there are alreay in -mm or linux-next? > > Forgot to add Matt, sorry for noise... Any of the changes that aren't in Linus' tree will be in -mm and linux-next. The ones currently in linux-next are, 07d969a parisc: use set_current_blocked() and block_sigmask() 5becb45 frv: use set_current_blocked() and block_sigmask() 3608417 blackfin: use set_current_blocked() and block_sigmask() cd21f1a unicore32: use block_sigmask() 2bb36fd h8300: use set_current_blocked() and block_sigmask() a624f4f score: use set_current_blocked() and block_sigmask() 2326e2e score: don't mask signals if we fail to setup signal stack b2f6181 microblaze: use set_current_blocked() and block_sigmask() f557a56 microblaze: fix signal masking 9ff7b4a microblaze: no need to reset handler if SA_ONESHOT 6cb49f5 microblaze: don't reimplement force_sigsegv() bd9767f ia64: use set_current_blocked() and block_sigmask() cdbc96c cris: use set_current_blocked() and block_sigmask() 295f127 mn10300: use set_current_blocked() and block_sigmask() 524987e m68k: use set_current_blocked() and block_sigmask() f0c96a3 m32r: use set_current_blocked() and block_sigmask() f0f0acd avr32: use block_sigmask() ef64059 avr32: don't mask signals in the error path ... and this one from you, Oleg, that was sent as part of my series, 3e6c120 avr32: use set_current_blocked() in handle_signal/sys_rt_sigreturn -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
