openslx/kernel-qcow2-linux.git - In-kernel qcow2 (Kernel part)

	Commit message (Collapse)	Author	Age	Files	Lines
*	ocfs2: make struct ocfs2_control_device static	Adrian Bunk	2008-05-01	1	-1/+1
\| \| \| \| \| \| \| \| \|	This patch makes the needlessly global struct ocfs2_control_device static. Signed-off-by: Adrian Bunk <bunk@kernel.org> Acked-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: add fsdlm to stackglue	David Teigland	2008-04-18	1	-1/+215
\| \| \| \| \| \| \| \| \| \|	Add code to use fs/dlm. [ Modified to be part of the stack_user module -- Joel ] Signed-off-by: David Teigland <teigland@redhat.com> Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: Add the 'set version' message to the ocfs2_control device.	Joel Becker	2008-04-18	1	-12/+119
\| \| \| \| \| \| \| \| \|	The "SETV" message sets the filesystem locking protocol version as negotiated by the client. The client negotiates based on the maximum version advertised in /sys/fs/ocfs2/max_locking_protocol. Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: Add the local node id to the handshake.	Joel Becker	2008-04-18	1	-49/+173
\| \| \| \| \| \| \| \| \|	This is the second part of the ocfs2_control handshake. After negotiating the ocfs2_control protocol, the daemon tells the filesystem what the local node id is via the SETN message. Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: Introduce the DOWN message to ocfs2_control	Joel Becker	2008-04-18	1	-5/+89
\| \| \| \| \| \| \| \|	When the control daemon sees a node go down, it sends a DOWN message through the ocfs2_control device. Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: Start the ocfs2_control handshake.	Joel Becker	2008-04-18	1	-5/+139
\| \| \| \| \| \| \| \| \| \| \| \| \|	When a control daemon opens the ocfs2_control device, it must perform a handshake to tell the filesystem it is something capable of monitoring cluster status. Only after the handshake is complete will the filesystem allow mounts. This is the first part of the handshake. The daemon reads all supported ocfs2_control protocols, then writes in the protocol it will use. Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: Add the ocfs2_control misc device.	Joel Becker	2008-04-18	1	-1/+183
\| \| \| \| \| \| \| \|	The ocfs2_control misc device is how a userspace control daemon (controld) talks to the filesystem. Introduce the bare-bones filesystem ops. Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
*	ocfs2: Add the user stack module.	Joel Becker	2008-04-18	1	-0/+38
	Add a skeleton for the stack_user module. It's just the barebones module code. Signed-off-by: Joel Becker <joel.becker@oracle.com> Signed-off-by: Mark Fasheh <mfasheh@suse.com>