linux-kernel - Re: [RFC] O_NOACC: open without any access

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: <5666.1245797092@redhat.com>
Date:	Tue, 23 Jun 2009 23:44:52 +0100
From:	David Howells <dhowells@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	dhowells@...hat.com, Miklos Szeredi <miklos@...redi.hu>,
	alan@...rguk.ukuu.org.uk, hch@...radead.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	viro@...IV.linux.org.uk, adilger@....com, akpm@...ux-foundation.org
Subject: Re: [RFC] O_NOACC: open without any access

Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> That said, I do _not_ like the notion of
> 
> 	> Add a new inode->i_filesystem_fop pointer
> 
> regardless of whether it's in inode->i_op or wherever. I think we should 
> just handle this in the regular "inode->f_op->open" routine, the same way 
> we handle FMODE_EXCLUSIVE (O_EXCL), FMODE_NDELAY (O_NONBLOCK) and lack of 
> access rights (O_NOACCESS) in the driver open routines that currently 
> handle those specially (O_NDELAY is spe

Did you accidentally delete more than the word 'special' there?

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/