linux-kernel - Re: [PATCHv2 2/5] VFS: DazukoFS, stackable-fs, file access control

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:	Fri, 13 Feb 2009 20:33:33 +0100
From:	John Ogness <dazukocode@...ess.net>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
	malware-list@...ts.printk.net, eparis@...hat.com,
	hch@...radead.org, alan@...rguk.ukuu.org.uk
Subject: Re: [PATCHv2 2/5] VFS: DazukoFS, stackable-fs, file access control

On 2009-02-12, Jan Engelhardt <jengelh@...ozas.de> wrote:
>>+By opening the device /dev/dazukofs.0 an application has registered itself.
>>+A read on the device will block until a file access event on DazukoFS has
>>+taken place. When a file access event has occured, the read will return with
>>+information about the file access event. For example:
>
> Given that there are more device files to come, I would
> put this into a separate directory, /dev/dazukofs/0, much
> like dm-crypt does for its devices.

I was not sure if I should leave it up to udev rules to organize
things. I agree that putting everything under a directory is cleaner.
I will make this change for the next patch series.

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