linux-kernel - Re: [PATCH 2/2] signals: document CLD

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20080312220213.396DA26F992@magilla.localdomain>
Date:	Wed, 12 Mar 2008 15:02:13 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Oleg Nesterov <oleg@...sign.ru>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Pavel Emelyanov <xemul@...nvz.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] signals: document CLD_CONTINUED notification mechanics

> A couple of small comments about how CLD_CONTINUED notification works.

A worthy addition.  I would make the get_signal_to_deliver comment say a
little more.  In particular, it's kind of nonobvious that though this
happens at the beginning of the function, the importance of its placement
is really that it will always be run (via the relock: loop) just after any
wake-up from having been in TASK_STOPPED.

Thanks,
Roland
--
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/