linux-kernel - Re: [PATCH 11/59] CRED: Wrap task credential accesses in video input drivers

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: <20080829193227.1494de9b@mchehab.chehab.org>
Date:	Fri, 29 Aug 2008 19:32:27 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	David Howells <dhowells@...hat.com>,
	Serge Hallyn <serue@...ibm.com>, video4linux-list@...hat.com
Subject: Re: [PATCH 11/59] CRED: Wrap task credential accesses in video
 input drivers

On Wed, 27 Aug 2008 14:46:39 +0100
David Howells <dhowells@...hat.com> wrote:

> Wrap access to task credentials so that they can be separated more easily from
> the task_struct during the introduction of COW creds.
> 
> Change most current->(|e|s|fs)[ug]id to current_(|e|s|fs)[ug]id().
> 
> Change some task->e?[ug]id to task_e?[ug]id().  In some places it makes more
> sense to use RCU directly rather than a convenient wrapper; these will be
> addressed by later patches.
> 
> Signed-off-by: David Howells <dhowells@...hat.com>
> Reviewed-by: James Morris <jmorris@...ei.org>
> Acked-by: Serge Hallyn <serue@...ibm.com>
> Cc: Mauro Carvalho Chehab <mchehab@...radead.org>

Acked-by: Mauro Carvalho Chehab <mchehab@...radead.org>

I'll add it on my tree and keep it for linux-next.

Cheers,
Mauro
--
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/