[evlog-dev] netlink-based kernel support for evlog

As you may know, over the past year and a half, we've proposed a variety of
mechanisms for enabling the Linux kernel to log events to evlog.  Until
recently, we've always proposed that kernel events would be written to a
static buffer in the kernel, then drained from the buffer and logged by
evlogd.

This spring, it was proposed that netlink serve as the kernel-to-user
transport mechanism (complementary to printk, of course) for kernel error
information.  Dave Miller postulated a new netlink protocol,
NETLINK_KERROR, and coded a prototype.  Several people have expressed
support for this idea.  This week I posted a revised version of Dave's
patch, plus another patch that implements a simple API that uses Dave's
protocol to log evlog-compatible events.

If you would like to read more about this, please see the subject
    "[PATCH - RFC] [1/2] 2.6 must-fix list - kernel error reporting"
on the Linux Kernel Mailing List.  Feel free to comment.

Note that, in an attempt to keep the proposal simple, we've left out some
of the features that we implemented previously -- for example, printk
forwarding, attribute naming/automatic template generation, evl_writek,
facility registration, etc.  If you depend on any of these features, let me
know.

Thanks.
Jim Keniston



-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1