linux-kernel - Re: [PATCH 0/1] (Was: [regression] boot failure on alpha, bisected)

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] [day] [month] [year] [list]

Date:	Sun, 14 Oct 2012 20:42:18 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	dl8bcu@...bcu.de, peterz@...radead.org, mingo@...nel.org,
	linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/1] (Was: [regression] boot failure on alpha, bisected)

On 10/14, Oleg Nesterov wrote:
>
> Again, this is fine. But why "else" ? It seems that
>
> 			if (thread_flags & _TIF_SIGPENDING) {
> 				do_signal(regs, r0, r19);
> 				r0 = 0;
> 			}
>
> 			if (thread_flags & _TIF_NOTIFY_RESUME) {
> 				clear_thread_flag(TIF_NOTIFY_RESUME);
> 				tracehook_notify_resume(regs);
> 			}
>
> makes a bit more sense?

Except I meant "if (_TIF_NOTIFY_RESUME)" first.

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/