[MODERATED] Re: [PATCH v6 31/43] MDSv6

[Andi Kleen <ak@linux.intel.com>]

> Then why are you messing around with the usbmon callback?  It has
> nothing to do with anything here.  By hooking it here, you now have 2
> calls to this function on the USB urb callback path.

Ok so where should it be hooked instead?

> The fact that a root process happens to be watching the USB data flowing
> through the system, or not, should have no affect on anything here, as
> the data flow is still the same (with the exception an extra copy in the
> irq could happen).  

My impression was that the usbmon copy is the only copy in interrupt context?
Was that wrong? If there's another copy in interrupt context yes it would
need to be instrumented too.

> As I asked with the hcd change, what is "user data"?

Here's the latest definition from clearcpu.txt

In this case I assume it includes non header data,
so would need to be protected.

User data is sensitive, but only for other processes.

User data is anything in the user address space, or data buffers
directly copied from/to the user (e.g. read/write). It does not
include metadata, or flag settings. For example packet headers
or file names are not sensitive in this model.

Block IO data (but not meta data) is sensitive.

We consider data from input devices (such as key presses)
sensitive. We also consider sound data or terminal
data sensitive.

-Andi