linux/fs/gfs2/locking/dlm
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>
2009-01-05 07:39:15 +00:00
..
lock_dlm.h [GFS2] Fix module building 2008-06-27 09:40:57 +01:00
lock.c [GFS2] Remove all_list from lock_dlm 2008-06-27 09:39:50 +01:00
main.c dlm: move plock code from gfs2 2008-04-21 11:22:28 -05:00
Makefile dlm: move plock code from gfs2 2008-04-21 11:22:28 -05:00
mount.c GFS2: Send useful information with uevent messages 2009-01-05 07:39:15 +00:00
sysfs.c GFS2: Send some sensible sysfs stuff 2009-01-05 07:39:10 +00:00
thread.c [GFS2] Remove remote lock dropping code 2008-06-27 09:39:44 +01:00