linux-kernel - Re: [PATCH 41/41] exit: Use __set_task

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Aug 2011 20:06:44 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Matt Fleming <matt@...sole-pimps.org>
Cc:	linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 41/41] exit: Use __set_task_blocked()

On 08/11, Matt Fleming wrote:
>
> As described in e6fa16ab ("signal: sigprocmask() should do
> retarget_shared_pending()") the modification of current->blocked is
> incorrect as we need to check whether the signal we're about to block
> is pending in the shared queue.

Yes. but in this case the code is correct. First of all, unblocking
is always fine. Also, this should be used by kthreads only, and they
are single-threaded.

But there are other reasons why I don't like this change, even if we
ignore the fact the patched exit.c can't be compiled (__set_task_blocked
is not exported ;).

>  int allow_signal(int sig)
>  {
> +	sigset_t blocked;
> +
>  	if (!valid_signal(sig) || sig < 1)
>  		return -EINVAL;
>
>  	spin_lock_irq(&current->sighand->siglock);
>  	/* This is only needed for daemonize()'ed kthreads */

Exactly. And nowadays the daemonize()'ed kthreads should not play
with allow_signal().

And more, I think it is the time to kill daemonize(). Contrary to
what /bin/grep thinks, it has only one user.

In short: this code in allow_signal() should die. I'll try to send
the patches soon...

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/