8304d6f24c
Change how callbacks are recorded for locks. Previously, information about multiple callbacks was combined into a couple of variables that indicated what the end result should be. In some situations, we could not tell from this combined state what the exact sequence of callbacks were, and would end up either delivering the callbacks in the wrong order, or suppress redundant callbacks incorrectly. This new approach records all the data for each callback, leaving no uncertainty about what needs to be delivered. Signed-off-by: David Teigland <teigland@redhat.com>
19 lines
586 B
C
19 lines
586 B
C
/*
|
|
* Copyright (C) 2006-2010 Red Hat, Inc. All rights reserved.
|
|
*
|
|
* This copyrighted material is made available to anyone wishing to use,
|
|
* modify, copy, or redistribute it subject to the terms and conditions
|
|
* of the GNU General Public License v.2.
|
|
*/
|
|
|
|
#ifndef __USER_DOT_H__
|
|
#define __USER_DOT_H__
|
|
|
|
void dlm_user_add_ast(struct dlm_lkb *lkb, uint32_t flags, int mode,
|
|
int status, uint32_t sbflags, uint64_t seq);
|
|
int dlm_user_init(void);
|
|
void dlm_user_exit(void);
|
|
int dlm_device_deregister(struct dlm_ls *ls);
|
|
int dlm_user_daemon_available(void);
|
|
|
|
#endif
|