You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Steven Whitehouse 9a776db737 GFS2: Send useful information with uevent messages ... In order to distinguish between two differing uevent messages and to avoid using the (racy) method of reading status from sysfs in future, this adds some status information to our uevent messages. Btw, before anybody says "sysfs isn't racy", I'm aware of that, but the way that GFS2 was using it (send an ambiugous uevent and then expect the receiver to read sysfs to find out the status of the reported operation) was. The additional benefit of using the new interface is that it should be possible for a node to recover multiple journals at the same time, since there is no longer any confusion as to which journal the status belongs to. At some future stage, when all the userland programs have been converted, I intend to remove the old interface. Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>		16 years ago
..
Makefile	dlm: move plock code from gfs2	17 years ago
lock.c	[GFS2] Remove all_list from lock_dlm	17 years ago
lock_dlm.h	[GFS2] Fix module building	17 years ago
main.c	dlm: move plock code from gfs2	17 years ago
mount.c	GFS2: Send useful information with uevent messages	16 years ago
sysfs.c	GFS2: Send some sensible sysfs stuff	16 years ago
thread.c	[GFS2] Remove remote lock dropping code	17 years ago