linux-kernel - Re: [PATCH v3] vfs: new O

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: <20091205202838.3456b6fc@lxorguk.ukuu.org.uk>
Date:	Sat, 5 Dec 2009 20:28:38 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	Andy Lutomirski <luto@....edu>, miklos@...redi.hu,
	akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] vfs: new O_NODE open flag

> Maybe alan was worried about the O_NODE | O_RDWR, etc. case?  That
> simply doesn't make any sense for special files.

I am concerned primarily about the lack of ability to get rid of such a
handle in a controlled fashion. The udev/device unload case is simply one
obvious way to exploit it.

I still don't believe O_NODE makes sense without revoke(), and even then
needs huge amounts of care on the device side of things.
--
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/