linux-kernel - Re: [PATCH 07/37] Security: De-embed task security record from task and use refcounting

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]

Message-ID: <28534.1202751036@redhat.com>
Date:	Mon, 11 Feb 2008 17:30:36 +0000
From:	David Howells <dhowells@...hat.com>
To:	James Morris <jmorris@...ei.org>
Cc:	dhowells@...hat.com, Trond.Myklebust@...app.com,
	chuck.lever@...cle.com, nfsv4@...ux-nfs.org,
	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, selinux@...ho.nsa.gov,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 07/37] Security: De-embed task security record from task and use refcounting

James Morris <jmorris@...ei.org> wrote:

> > Remove the temporarily embedded task security record from task_struct.
> > Instead it is made to dangle from the task_struct::sec and
> > task_struct::act_as pointers with references counted for each.
> 
> ...
> 
> These patches are kind of huge.

Yeah, I know.  The problem is that each patch must compile and run.  They
can't be split up without violating that unfortunately.

> Why manually copy these fields after a kmemdup?

Fair point.  Fixed.

> What about the task backpointer? (i.e. tsec2->task)

The problem is that there can't be one with this patch as the task_security
struct and the LSM security data attached to it may outlive the task it points
back to.

It seems that the backpointer can be dispensed with.  Nothing particularly
seems to use it.  Do you know the reason for its existence?

David
--
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/