Searched hist:"921169 ca2f7c8a0a2ccda2ce33c465dfe3ae30ef" (Results 1 – 3 of 3) sorted by relevance
| /linux/fs/gfs2/ |
| H A D | glock.h | diff 921169ca2f7c8a0a2ccda2ce33c465dfe3ae30ef Mon Nov 29 13:50:38 CET 2010 Steven Whitehouse <swhiteho@redhat.com> GFS2: Clean up of gdlm_lock function
The DLM never returns -EAGAIN in response to dlm_lock(), and even
if it did, the test in gdlm_lock() was wrong anyway. Once that
test is removed, it is possible to greatly simplify this code
by simply using a "normal" error return code (0 for success).
We then no longer need the LM_OUT_ASYNC return code which can
be removed.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
|
| H A D | lock_dlm.c | diff 921169ca2f7c8a0a2ccda2ce33c465dfe3ae30ef Mon Nov 29 13:50:38 CET 2010 Steven Whitehouse <swhiteho@redhat.com> GFS2: Clean up of gdlm_lock function
The DLM never returns -EAGAIN in response to dlm_lock(), and even
if it did, the test in gdlm_lock() was wrong anyway. Once that
test is removed, it is possible to greatly simplify this code
by simply using a "normal" error return code (0 for success).
We then no longer need the LM_OUT_ASYNC return code which can
be removed.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
|
| H A D | glock.c | diff 921169ca2f7c8a0a2ccda2ce33c465dfe3ae30ef Mon Nov 29 13:50:38 CET 2010 Steven Whitehouse <swhiteho@redhat.com> GFS2: Clean up of gdlm_lock function
The DLM never returns -EAGAIN in response to dlm_lock(), and even
if it did, the test in gdlm_lock() was wrong anyway. Once that
test is removed, it is possible to greatly simplify this code
by simply using a "normal" error return code (0 for success).
We then no longer need the LM_OUT_ASYNC return code which can
be removed.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
|