linux-kernel - Re: [RFC 1/2] move binfmt filed to signal

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:	Wed, 22 Jul 2009 15:03:53 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>,
	linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...sign.ru>
Subject: Re: [RFC 1/2] move binfmt filed to signal_struct

> > Because the binfmt is not different between threads in the same process,
> > it can be moved from task_struct to signal_struct.
> 
> Seems like a logical cleanup to me.

IMHO binfmt belongs in mm_struct.

> We should rename signal_struct.

Indeed, it's in fact 'struct process'.  But historically Linus has objected
to admitting that there is really a concept of process in the POSIX sense
that exists deep in the implementation (as it truly does for years now),
beyond "tasks that happen to share a lot of CLONE_* stuff".  The name
signal_struct is sufficiently misleading to make it easier to retain the
fantasy he prefers. ;-)

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/