Re: [PATCH 20/40] mn10300: Use set_current_blocked() and block_sigmask()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2012-02-14 at 18:30 +0000, David Howells wrote:
> Matt Fleming <matt@xxxxxxxxxxxxxxxxx> wrote:
> 
> > > Can this line create a race, now that it's not protected by a lock?  It is
> > > possible for current->blocked to get altered by another thread.
> > 
> > ->blocked can only ever be altered by current, not another thread. See
> > the following comment from sigprocmask() in kernel/signal.c,
> 
> Okay, I've managed to convince myself.  Feel free to my Acked-by to the
> MN10300 and FRV patches.

Thanks! I think Andrew is picking these up, unless you want to take them
through the arch trees?

-- 
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


[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux