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]

Date:	Tue, 23 Jun 2009 18:31:23 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	dhowells@...hat.com
CC:	alan@...rguk.ukuu.org.uk, dhowells@...hat.com, miklos@...redi.hu,
	hch@...radead.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	viro@...IV.linux.org.uk, adilger@....com, akpm@...ux-foundation.org
Subject: Re: [RFC] O_NOACC: open without any access

On Tue, 23 Jun 2009, David Howells wrote:
> Reference count on which module?  This would not take a reference on
> the device driver as it would not refer to it, but would still have
> a file struct, an inode struct and a dentry struct on the underlying
> fs.

So how about the following: provide a new open flag O_FILESYSTEM,
meaning it opens the file on the underlying filesystem instead of the
device/socket/symlink/etc...

Add a new inode->i_filesystem_fop pointer which is used instead of
inode->i_fop in case if O_FILESYSTEM.  If ->i_filesystem_fop isn't set
by the filesystem, fall back to a default which returns -EBADF for all
operations (except open).

Define O_NOACC as 3.  On open(..., O_FILESYSTEM | O_NOACC) require no
privileges on the file.

AFS would set up i_filesystem_fop with its ->ioctl() function. No
special handling needed for revoke()...

That would work, no?

Thanks,
Miklos

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