From: Simon Wilkinson Date: Mon, 26 Oct 2009 12:49:11 +0000 (+0000) Subject: Clean up console message X-Git-Tag: openafs-stable-1_4_12pre1~102 X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=ad6dabdcc5b04f907c08213e46f346785e67a139;p=packages%2Fo%2Fopenafs.git Clean up console message Clean up the 'all buffers locked' console message so that it's clear that it comes from AFS, and so it has a trailing newline. From a bug report by Rainer Toebbicke to openafs-info Change-Id: I3f69e57e37a91ae3e6e8822ccfe72dddc06b4359 Reviewed-on: http://gerrit.openafs.org/732 Tested-by: Derrick Brashear Reviewed-by: Derrick Brashear (cherry picked from commit 4a006f167bf6fe550eac9c96c6fce1f538760709) Reviewed-on: http://gerrit.openafs.org/823 Reviewed-by: Dan Hyde --- diff --git a/src/afs/afs_buffer.c b/src/afs/afs_buffer.c index b2f81dc31..9e9d2db3b 100644 --- a/src/afs/afs_buffer.c +++ b/src/afs/afs_buffer.c @@ -335,7 +335,7 @@ afs_newslot(struct dcache *adc, afs_int32 apage, register struct buffer *lp) * seems extreme. To the best of my knowledge, all the callers * of DRead are prepared to handle a zero return. Some of them * just panic directly, but not all of them. */ - afs_warn("all buffers locked"); + afs_warn("afs: all buffers locked\n"); return 0; } @@ -545,7 +545,7 @@ shutdown_bufferpackage(void) /* The following check shouldn't be necessary and it will be removed soon */ if (!tp->bufp) afs_warn - ("shutdown_bufferpackage: bufp == 0!! Shouldn't happen\n"); + ("afs: shutdown_bufferpackage: bufp == 0!! Shouldn't happen\n"); else { brelse(tp->bufp); tp->bufp = 0;