The patch titled
fs: use appropriate printk priority levels
has been added to the -mm tree. Its filename is
fs-use-appropriate-printk-priority-level.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: fs: use appropriate printk priority levels
From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
printk()s without a priority level default to KERN_WARNING. To reduce
noise at KERN_WARNING, this patch set the priority level appriopriately
for unleveled printks()s. This should be useful to folks that look at
dmesg warnings closely.
Signed-off-by: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
Cc: Jens Axboe <axboe@xxxxxxxxx>
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/bio.c | 2 +-
fs/namespace.c | 2 +-
init/do_mounts.c | 3 ++-
3 files changed, 4 insertions(+), 3 deletions(-)
diff -puN fs/bio.c~fs-use-appropriate-printk-priority-level fs/bio.c
--- a/fs/bio.c~fs-use-appropriate-printk-priority-level
+++ a/fs/bio.c
@@ -111,7 +111,7 @@ static struct kmem_cache *bio_find_or_cr
if (!slab)
goto out_unlock;
- printk("bio: create slab <%s> at %d\n", bslab->name, entry);
+ printk(KERN_INFO "bio: create slab <%s> at %d\n", bslab->name, entry);
bslab->slab = slab;
bslab->slab_ref = 1;
bslab->slab_size = sz;
diff -puN fs/namespace.c~fs-use-appropriate-printk-priority-level fs/namespace.c
--- a/fs/namespace.c~fs-use-appropriate-printk-priority-level
+++ a/fs/namespace.c
@@ -2594,7 +2594,7 @@ void __init mnt_init(void)
if (!mount_hashtable)
panic("Failed to allocate mount hash table\n");
- printk("Mount-cache hash table entries: %lu\n", HASH_SIZE);
+ printk(KERN_INFO "Mount-cache hash table entries: %lu\n", HASH_SIZE);
for (u = 0; u < HASH_SIZE; u++)
INIT_LIST_HEAD(&mount_hashtable[u]);
diff -puN init/do_mounts.c~fs-use-appropriate-printk-priority-level init/do_mounts.c
--- a/init/do_mounts.c~fs-use-appropriate-printk-priority-level
+++ a/init/do_mounts.c
@@ -293,7 +293,8 @@ static int __init do_mount_root(char *na
sys_chdir((const char __user __force *)"/root");
ROOT_DEV = current->fs->pwd.mnt->mnt_sb->s_dev;
- printk("VFS: Mounted root (%s filesystem)%s on device %u:%u.\n",
+ printk(KERN_INFO
+ "VFS: Mounted root (%s filesystem)%s on device %u:%u.\n",
current->fs->pwd.mnt->mnt_sb->s_type->name,
current->fs->pwd.mnt->mnt_sb->s_flags & MS_RDONLY ?
" readonly" : "", MAJOR(ROOT_DEV), MINOR(ROOT_DEV));
_
Patches currently in -mm which might be from msb@xxxxxxxxxxxx are
fs-use-appropriate-printk-priority-level.patch
printk-allow-setting-default_message_level-via-kconfig.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
