Before that patch if we echo something into /dev/kmsg we get:
<4>[ 35.084348] testing
If we do it on or after that patch we get:
<12>[ 71.091005] test
This change makes sense from the commit message "All userspace-injected
messages enforce a
facility value > 0 now, to be able to reliably distinguish them from
the kernel-generated messages"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1274444
Title:
echo string to /dev/kmsg fails to appear on /var/log/syslog
Status in “linux” package in Ubuntu:
In Progress
Bug description:
[Impact]
In the precise 3.2 series kernel writing strings to /dev/kmsg appears and
dmesg and /var/log/syslog, in 3.5 series kernel this does not happen properly
even with the equivalent userspace packages.
I've already done a coarse bisect,
works v3.4
fails in v3.5-rc1
[Test Case]
Run the following script as root:
#!/bin/bash
STRING=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32)
> /var/log/syslog
echo $STRING > /dev/kmsg
sleep 5
grep $STRING /var/log/syslog
# This should return 0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
