On Sun, Mar 13, 2016 at 10:14:16PM -0400, Wade Mealing wrote: > Gday All, > > Seeking some advice, so I thought I'd talk to those involved about how I should go about this. > > I'd like to extend the device audit subsystem to log some of the > device additions/removals to the kernel Why? What are you going to do with this information? What is it going to be used for, are you going to act on it? > and figured that USB was a well maintained (and easily testable for > me) subsystem that I can start with. > > My initial plan of attack was to use the generic add_device > notifier_block call chain and extend it per bus type. > > The USB subsystem already accepts these events via usb_bus_notify ( > drivers/usb/core/usb.c ) and it would be a matter of adding an audit > function to this area. Why not have your audit code just register with the USB core to get the data this way? No need to modify any USB code at all. But again, what are you going to do with this information that userspace doesn't already have (hint, you are keeping track of all uevents, right?) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
