linux-kernel - [FOR REVIEW, PATCH 0/2] do

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

Date:	Wed, 6 May 2009 07:33:18 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Roland McGrath <roland@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: [FOR REVIEW, PATCH 0/2] do_wait() cleanups.

While this is not strictly necessary, I'd like to also cleanup do_wait/etc
before changing ptrace internals. Just because this code is still hardly
readable, imho. And we are going to complicate this code a little bit.

This trivial change nearly killed me. I didn't expect I will spent all
night doing this!!!

The patch is not tested, I am sending it for the early review, because
before I do the next changes I'd like to know your opinion: do you agree
with this patch "in general" ?

If yes, I'll send the next trivial cleanups on top:

	- factor out getrusage() code

	- factor out infop filling

	- simplify retval/notask_error interaction

	- perhaps some small simplifications in do_wait's callers

Naming. I agree in advance with any changes you suggest, and this is
another reason I am sending it early.

Also. This is completely off-topic wrt ptrace cleanups, but if we
change do_wait() now perhaps it makes sense to optimize do_wait()
in PIDTYPE_PID case. In this case we do not need to scan the lists,
we can inspect the task directly. This change should be simple, but
it will increase .text. Do you think it makes sense?

I do not plan any other cleanups before changing ptrace internals.

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/