linux-kernel - Re: [patch 0/6] sys_indirect RFC

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

Date:	Mon, 2 Jul 2007 17:28:08 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"Davide Libenzi" <davidel@...ilserver.org>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>
Subject: Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction

On 7/2/07, Davide Libenzi <davidel@...ilserver.org> wrote:
> Never be usable? I made you a concrete example that is like 8 months old.
> And *that* could not have been cleanly handled with the flat structure
> idea.

First of all, sigmasks are not widely needed.  Second, why on earth
shouldn't it be possible with a flat structure?  Just have the sigmask
in the same position.  It's no magic.

> But there are
> examples (and the signal stuff is one of them), where you do need the
> set_context+syscall+unset_context abstraction, for all cases where the
> kernel already has its own internal data strctures. In those cases you'd
> have to spread sys_internal context knowledge all around the kernel,
> whereas the current solution allows you to confine the code inside
> kernel/indirect.c

Nonsense.  Whether you have a new word in the task structure or a
pointer to a structure, you have to embed knowledge of this
indirection in every affected code paths.  There is no difference
here.  The only difference is that trying to force everything through
an artificially complicated common entry code.

I hope that Andrew+Linus will see through this.  I'm done arguing.
-
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/