summaryrefslogtreecommitdiff
path: root/fs/afs/server.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2020-10-15 11:02:25 +0300
committerDavid Howells <dhowells@redhat.com>2020-10-16 16:39:34 +0300
commit7530d3eb3dcf1a30750e8e7f1f88b782b96b72b8 (patch)
treec401bd777e982a5f939c1906756ea9192852f5fc /fs/afs/server.c
parentdca54a7bbb8ca9148ae10d60c66c926e222a9c4b (diff)
downloadlinux-7530d3eb3dcf1a30750e8e7f1f88b782b96b72b8.tar.xz
afs: Don't assert on unpurgeable server records
Don't give an assertion failure on unpurgeable afs_server records - which kills the thread - but rather emit a trace line when we are purging a record (which only happens during network namespace removal or rmmod) and print a notice of the problem. Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'fs/afs/server.c')
-rw-r--r--fs/afs/server.c7
1 files changed, 6 insertions, 1 deletions
diff --git a/fs/afs/server.c b/fs/afs/server.c
index e82e452e2612..684a2b02b9ff 100644
--- a/fs/afs/server.c
+++ b/fs/afs/server.c
@@ -550,7 +550,12 @@ void afs_manage_servers(struct work_struct *work)
_debug("manage %pU %u", &server->uuid, active);
- ASSERTIFCMP(purging, active, ==, 0);
+ if (purging) {
+ trace_afs_server(server, atomic_read(&server->ref),
+ active, afs_server_trace_purging);
+ if (active != 0)
+ pr_notice("Can't purge s=%08x\n", server->debug_id);
+ }
if (active == 0) {
time64_t expire_at = server->unuse_time;