linux-kernel - Re: [PATCH] eCryptfs: Do not try to open device files on mknod

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080711121729.af5750de.akpm@linux-foundation.org>
Date:	Fri, 11 Jul 2008 12:17:29 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Michael Halcrow <mhalcrow@...ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] eCryptfs: Do not try to open device files on mknod

On Wed, 9 Jul 2008 17:21:48 -0500 Michael Halcrow <mhalcrow@...ibm.com> wrote:

> When creating device nodes, eCryptfs needs to delay actually opening
> the lower persistent file until an application tries to open. Device
> handles may not be backed by anything when they first come into
> existence.

Generates a reject against your eariler
ecryptfs-privileged-kthread-for-lower-file-opens.patch.

It was easy enough to fix, but I'd sugest that you raise and test new
patches against at least the other pending ones, rather than against virgin
mainline.  Because stuff happens...
--
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/