summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2011-05-08 19:37:54 -0400
committerTheodore Ts'o <tytso@mit.edu>2011-05-08 19:37:54 -0400
commit1be2add685181ba31554ffefa428b0f80a408bff (patch)
tree1556ae76056f50460af2db7018816b96b4676c63
parent229309caebe4508d650bb6d8f7d51f2b116f5bbd (diff)
downloadlinux-3.10-1be2add685181ba31554ffefa428b0f80a408bff.tar.gz
linux-3.10-1be2add685181ba31554ffefa428b0f80a408bff.tar.bz2
linux-3.10-1be2add685181ba31554ffefa428b0f80a408bff.zip
jbd2: only print the debugging information for tid wraparound once
If we somehow wrap, we don't want to keep printing the warning message over and over again. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
-rw-r--r--fs/jbd2/journal.c9
1 files changed, 5 insertions, 4 deletions
diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index 8c10004f787..cd2d341f602 100644
--- a/fs/jbd2/journal.c
+++ b/fs/jbd2/journal.c
@@ -500,10 +500,11 @@ int __jbd2_log_start_commit(journal_t *journal, tid_t target)
/* This should never happen, but if it does, preserve
the evidence before kjournald goes into a loop and
increments j_commit_sequence beyond all recognition. */
- WARN(1, "jbd: bad log_start_commit: %u %u %u %u\n",
- journal->j_commit_request, journal->j_commit_sequence,
- target, journal->j_running_transaction ?
- journal->j_running_transaction->t_tid : 0);
+ WARN_ONCE(1, "jbd: bad log_start_commit: %u %u %u %u\n",
+ journal->j_commit_request,
+ journal->j_commit_sequence,
+ target, journal->j_running_transaction ?
+ journal->j_running_transaction->t_tid : 0);
return 0;
}