summaryrefslogtreecommitdiffstats
path: root/fs/gfs2/bmap.c
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2008-11-27 09:42:51 +0000
committerSteven Whitehouse <swhiteho@redhat.com>2009-01-05 07:39:15 +0000
commit9a776db7371b9c77a8f4f0d2ac6374d78ac7db7d (patch)
tree5863e73d8b84c35fe4223831c2c3f30ec23f6d9f /fs/gfs2/bmap.c
parent3af165ac4d099385b12e3e75a9ee3ffd02da33e0 (diff)
downloadop-kernel-dev-9a776db7371b9c77a8f4f0d2ac6374d78ac7db7d.zip
op-kernel-dev-9a776db7371b9c77a8f4f0d2ac6374d78ac7db7d.tar.gz
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>
Diffstat (limited to 'fs/gfs2/bmap.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud