| 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
| ||
|
Message-ID: <alpine.LSU.2.00.0902121659460.5658@fbirervta.pbzchgretzou.qr> Date: Thu, 12 Feb 2009 17:00:54 +0100 (CET) From: Jan Engelhardt <jengelh@...ozas.de> To: John Ogness <dazukocode@...ess.net> 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 Tuesday 2009-02-03 20:17, John Ogness wrote: >Index: linux-2.6.28/Documentation/filesystems/dazukofs.txt >=================================================================== >--- linux-2.6.28.orig/Documentation/filesystems/dazukofs.txt 2009-02-03 18:07:44.000000000 +0100 >+++ linux-2.6.28/Documentation/filesystems/dazukofs.txt 2009-02-03 18:10:46.000000000 +0100 >@@ -2,9 +2,10 @@ >+ >+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. -- 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/
Powered by blists - more mailing lists