summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexander Aring <aahringo@redhat.com>2021-03-01 17:05:08 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-05-19 10:12:52 +0200
commit06d59d21cb05765e72a53b53a86c6be106bece88 (patch)
tree2137e24b542a61f05efeb1578b7d5100f4013e5c
parentbd6017a942b9343c1e6a99eef9c64fa264a1a53b (diff)
downloadlinux-stable-06d59d21cb05765e72a53b53a86c6be106bece88.tar.gz
linux-stable-06d59d21cb05765e72a53b53a86c6be106bece88.tar.bz2
linux-stable-06d59d21cb05765e72a53b53a86c6be106bece88.zip
fs: dlm: fix debugfs dump
[ Upstream commit 92c48950b43f4a767388cf87709d8687151a641f ] This patch fixes the following message which randomly pops up during glocktop call: seq_file: buggy .next function table_seq_next did not update position index The issue is that seq_read_iter() in fs/seq_file.c also needs an increment of the index in an non next record case as well which this patch fixes otherwise seq_read_iter() will print out the above message. Signed-off-by: Alexander Aring <aahringo@redhat.com> Signed-off-by: David Teigland <teigland@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
-rw-r--r--fs/dlm/debug_fs.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/dlm/debug_fs.c b/fs/dlm/debug_fs.c
index d6bbccb0ed15..d5bd990bcab8 100644
--- a/fs/dlm/debug_fs.c
+++ b/fs/dlm/debug_fs.c
@@ -542,6 +542,7 @@ static void *table_seq_next(struct seq_file *seq, void *iter_ptr, loff_t *pos)
if (bucket >= ls->ls_rsbtbl_size) {
kfree(ri);
+ ++*pos;
return NULL;
}
tree = toss ? &ls->ls_rsbtbl[bucket].toss : &ls->ls_rsbtbl[bucket].keep;