diff options
author | Alexander Aring <aahringo@redhat.com> | 2022-06-22 14:45:22 -0400 |
---|---|---|
committer | David Teigland <teigland@redhat.com> | 2022-08-01 09:31:32 -0500 |
commit | 81eeb82fc215afec7a0511dd5eab6b9cac8dac39 (patch) | |
tree | cf4364c835ec7f79fa487e1464fb0b46ba762d05 /crypto/aead.c | |
parent | 8d614a4457f5515be54dca6f0b95b6a9f968a888 (diff) | |
download | linux-stable-81eeb82fc215afec7a0511dd5eab6b9cac8dac39.tar.gz linux-stable-81eeb82fc215afec7a0511dd5eab6b9cac8dac39.tar.bz2 linux-stable-81eeb82fc215afec7a0511dd5eab6b9cac8dac39.zip |
fs: dlm: add deprecation Kconfig and warnings for timeouts
This patch adds a CONFIG_DLM_DEPRECATED_API Kconfig option
that must be enabled to use two timeout-related features
that we intend to remove in kernel v6.2. Warnings are
printed if either is enabled and used. Neither has ever
been used as far as we know.
. The DLM_LSFL_TIMEWARN lockspace creation flag will be
removed, along with the associated configfs entry for
setting the timeout. Setting the flag and configfs file
would cause dlm to track how long locks were waiting
for reply messages. After a timeout, a kernel message
would be logged, and a netlink message would be sent
to userspace. Recently, midcomms messages have been
added that produce much better logging about actual
problems with messages. No use has ever been found
for the netlink messages.
. The userspace libdlm API has allowed the DLM_LKF_TIMEOUT
flag with a timeout value to be set in lock requests.
The lock request would be cancelled after the timeout.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'crypto/aead.c')
0 files changed, 0 insertions, 0 deletions