-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check that console contents are initialized #55
Comments
Not sure about this particular error report, but the currently reproducible one:
seems to be an actual bug in Checking uninit printk arguments is doable, yet requires some changes to printk implementation. |
There's been a bunch of printk changes in the past years, I think we are better at reporting bugs in printk() now |
Example report below. We only detect the uninit when we read out console output from /dev/kmsg. If we don't read it out, we don't detect it. Even if we do, we detect it too late and attribute all such info leaks to do_syslog. We should detect them right in printk and attribute to the function that prints uninits.
The text was updated successfully, but these errors were encountered: