From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-19.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5FF23C4363C for ; Wed, 5 May 2021 17:10:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 39C0261155 for ; Wed, 5 May 2021 17:10:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238802AbhEERJq (ORCPT ); Wed, 5 May 2021 13:09:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:46458 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237413AbhEERAM (ORCPT ); Wed, 5 May 2021 13:00:12 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 1E80B619C0; Wed, 5 May 2021 16:40:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1620232806; bh=lBp3f5LDs3ZwVf5n60dmCuEVqvWqm3314S221/UgQ5I=; h=From:To:Cc:Subject:Date:From; b=ObFmooqnIStZbr8GY78zaZshtfIPxr7jU1uNDFnRIF2plPoiFGNv0nUsrE5Uo6869 HKNY9oyJKtjyvRjulpfm9B1NKfapjK5UkTUDs4JKlOzVr8maifkt+VfYPSzWHUaq9F nxkRujncK27bytdZBEoji4UPnp/ffdNk5Z0y6W1vVOYO0ci3AAmhtu3Je2Ik11/PaH kPopJfrPyiQpworBxyKFWiN7k/p5jl9KtKDx0UfshzX1BTEzBGqVsk7Mtz6w2QpIxR nb9uon2hoFLMmI8eauP6lVWYNWo5REPtRyfxK8hZs4akQLWgIrQTQCy/P4Cvbxp7hP DWtJe7hyp2AVQ== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Alexander Aring , David Teigland , Sasha Levin , cluster-devel@redhat.com Subject: [PATCH AUTOSEL 4.19 01/32] fs: dlm: fix debugfs dump Date: Wed, 5 May 2021 12:39:33 -0400 Message-Id: <20210505164004.3463707-1-sashal@kernel.org> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alexander Aring [ 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 Signed-off-by: David Teigland Signed-off-by: Sasha Levin --- fs/dlm/debug_fs.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/dlm/debug_fs.c b/fs/dlm/debug_fs.c index fa08448e35dd..bb87dad03cd4 100644 --- a/fs/dlm/debug_fs.c +++ b/fs/dlm/debug_fs.c @@ -544,6 +544,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; -- 2.30.2