linux-kernel - Re: [2/3] POHMELFS: Documentation.

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: <20080712070150.GD13483@ucw.cz>
Date:	Sat, 12 Jul 2008 09:01:51 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Evgeniy Polyakov <johnpol@....mipt.ru>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [2/3] POHMELFS: Documentation.

Hi!

> + * Completely async processing of all events (hard, symlinks and rename are the
> + 	only exceptions) including object creation and data reading and writing.

Hmm... this is little funny.

	Async processing of most events (only exceptions are ...) ?


> +POHMELFS network protocol.
> +
> +Basic structure used in network communication is following command:
> +
> +struct netfs_cmd
> +{
> +	__u16			cmd;	/* Command number */
> +	__u16			csize;	/* Attached crypto information size */
> +	__u16			cpad;	/* Attached padding size */
> +	__u16			ext;	/* External flags */
> +	__u32			size;	/* Size of the attached data */
> +	__u32			trans;	/* Transaction id */
> +	__u64			id;	/* Object ID to operate on. Used for feedback.*/
> +	__u64			start;	/* Start of the object. */
> +	__u64			iv;	/* IV sequence */
> +	__u8			data[0];
> +};

Which endianity?

							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/