linux-kernel - Re: [PATCH] CRED: Fix regression in cap_capable() as shown up by sys

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:	Sat, 3 Jan 2009 21:03:34 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	David Howells <dhowells@...hat.com>
Cc:	Christoph Hellwig <hch@....de>, jmorris@...ei.org,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] CRED: Fix regression in cap_capable() as shown up by
	sys_faccessat() [ver #2]

On Sat, Jan 03, 2009 at 11:03:26PM +0000, David Howells wrote:
> J. Bruce Fields <bfields@...ldses.org> wrote:
> 
> > More precisely:
> > 	- The last working commit is b6dff3ec... "CRED: Separate task
> > 	  security context from task_struct".
> > 	- The first commit exhibiting the permissions problem is
> > 	  a6f76f2... "CRED: Make execve() take advantage of
> > 	  copy-on-write credentials".
> > 	- The 9 commits in between (from f1752eec to d84f4f9) result in
> > 	  a soft lookup on boot.
> 
> Okay, I'll have a look at that, but did you manage to find out if the patch I
> posted fixed the problem you originally mentioned?

I tested that patch, yes, but it didn't fix the problem.

--b.
--
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/