Paolo Abeni [off-list ref] writes:

In non trivial scenarios, the action id alone is not sufficient
to identify the program causing the warning. Before the previous
patch, the generated stack-trace pointed out at least the
involved device driver.

Let's additionally include the program name and id, and the
relevant device name.

If the user needs additional infos, he can fetch them via a
kernel probe, leveraging the arguments added here.

v2  -> v3:
 - properly check NULL dev argument (kernel test robot)

v1  -> v2
  - do not include the device name for maps caller (Toke)

rfc -> v1:
 - do not print the attach type, print the program name

Signed-off-by: Paolo Abeni <pabeni@redhat.com>

You forgot my ack :) here it is again:

Acked-by: Toke Høiland-Jørgensen <redacted>