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 <shadow@dementia.org>
Reviewed-by: Derrick Brashear <shadow@dementia.org>
(cherry picked from commit 4a006f167bf6fe550eac9c96c6fce1f538760709)
Reviewed-on: http://gerrit.openafs.org/823
Reviewed-by: Dan Hyde <drh@umich.edu>

diff --git a/src/afs/afs_buffer.c b/src/afs/afs_buffer.c
index 1533f4dafd3f112a60ecf9405c78239f8a4636aa..0d1daa4d0b2c78377714b6e47a901bcd4d308584 100644 (file)
--- a/src/afs/afs_buffer.c
+++ b/src/afs/afs_buffer.c
@@ -337,7 +337,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;
     }
 
@@ -547,7 +547,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;