forked from Minki/linux
2c3fa6ae4d
This patch adds a WARN_ON() check to validate the right context while
dlm_midcomms_close() is called. Even before commit 489d8e559c
("fs: dlm: add reliable connection if reconnect") in this context
dlm_lowcomms_close() flushes all ongoing transmission triggered by dlm
application stack. If we do that, it's required that no new message will
be triggered by the dlm application stack. The function
dlm_midcomms_close() is not called often so we can check if all
lockspaces are in such context.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
26 lines
940 B
C
26 lines
940 B
C
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
/******************************************************************************
|
|
*******************************************************************************
|
|
**
|
|
** Copyright (C) Sistina Software, Inc. 1997-2003 All rights reserved.
|
|
** Copyright (C) 2004-2005 Red Hat, Inc. All rights reserved.
|
|
**
|
|
**
|
|
*******************************************************************************
|
|
******************************************************************************/
|
|
|
|
#ifndef __LOCKSPACE_DOT_H__
|
|
#define __LOCKSPACE_DOT_H__
|
|
|
|
int dlm_lockspace_init(void);
|
|
void dlm_lockspace_exit(void);
|
|
struct dlm_ls *dlm_find_lockspace_global(uint32_t id);
|
|
struct dlm_ls *dlm_find_lockspace_local(void *id);
|
|
struct dlm_ls *dlm_find_lockspace_device(int minor);
|
|
void dlm_put_lockspace(struct dlm_ls *ls);
|
|
void dlm_stop_lockspaces(void);
|
|
void dlm_stop_lockspaces_check(void);
|
|
|
|
#endif /* __LOCKSPACE_DOT_H__ */
|
|
|