Hi, (2014/05/20 12:36), [email protected] wrote:
On Mon, 19 May 2014 19:28:38 +0900, Yoshihiro YUNOMAE said:The header information is changed as follows: <prefix>,<seq#>,<timestamp>,<fragmented>,<PID>/<interrupt context>;<msg>Has this been tested with popular userspace that reads /dev/kmsg, to make sure that it actually plays nice with a 5th field being added? Yes, I know
I checked it for systemd-journald and rsyslog on the source code level, those tools don't handle new flag and field before ';' in the header of /dev/kmsg. Those tools use only log level, sequence#, and timestamp. So, even if we add these new flag and field for each message, those tools will be able to work. But, we'll fix this issue by other method if we found it in any subsystems except for the SCSI layer. (In the SCSI layer, we'll tackle this issue by using tracing feature.) Thank you, Yoshihiro YUNOMAE -- Yoshihiro YUNOMAE Software Platform Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: [email protected] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
