在dmesg中打印_为什么printk不在内核日志中打印消息（dmesg）

最新推荐文章于 2024-03-15 17:30:47 发布

糯嘛

最新推荐文章于 2024-03-15 17:30:47 发布

阅读量421

点赞数

文章标签：在dmesg中打印

本文链接：https://blog.csdn.net/weixin_31054839/article/details/111919590

版权

本文探讨了在Ubuntu 14.04上编写的一个小型内核模块，发现使用insmod加载模块时printk消息不会出现在dmesg中，但在使用rmmod卸载模块后会显示所有消息。问题在于printk中的换行符后有一个空格，导致消息未被立即刷新到内核日志。通过对vprintk_emit和log_output的分析，了解到内核日志缓冲区的行为类似于行缓冲，需要尾随换行符才能触发消息刷新。

摘要由CSDN通过智能技术生成

I wrote small kernel module code as mentioned below,

I am testing it in ubuntu 14.04

#include

int init_mod_func(void)

{

printk(KERN_INFO "My module inserted\n ");

return 0;

}

void cleanup_mod_func(void)

{

printk(KERN_INFO "My module removed\n ");

}

module_init(init_mod_func);

module_exit(cleanup_mod_func);

MODULE_AUTHOR("Ankur");

MODULE_DESCRIPTION("TEST MODULE");

MODULE_LICENSE("GPL");

Now when I compile and insert above module using insmod I don't see printk message in the dmesg. However after module removal using rmmod I see both the printk messages.

With closure look, I found out that it is happening because of space after \n in the printk.

However I don't get why it is like that.

ankur:~/temp/tmp$

ankur:~/temp/tmp$ sudo dmesg -C /dev/null

ankur:~/temp/tmp$

ankur:~/temp/tmp$ sudo insmod testmod.ko

ankur:~/temp/tmp$ dmesg

ankur:~/temp/tmp$

ankur:~/temp/tmp$ sudo rmmod testmod

ankur:~/temp/tmp$ dmesg

[ 4062.140441] My module inserted

[ 4062.140441]

[ 4073.324994] My module removed

[ 4073.324994]

解决方案

The kernel log ring buffer behaves as if it were line-buffered, as it can be seen in the implementation:

in vprintk_emit you can see how it marks a buffer to be flushed/buffered based on the existence of a trailing newline

in log_output you can see the actual code which takes care of flushing or buffering the message

As it is evident, your messages do not contain trailing newlines. Had you deleted the trailing space, you would see the messages in the kernel log after they had been flushed in the printk call(s).