Home
last modified time | relevance | path

Searched hist:"5 d92a30e900dc97221e36f09ae740457d560d281" (Results 1 – 2 of 2) sorted by relevance

/linux/include/trace/events/
H A Ddlm.hdiff 5d92a30e900dc97221e36f09ae740457d560d281 Wed Jun 22 20:45:12 CEST 2022 Alexander Aring <aahringo@redhat.com> fs: dlm: add resource name to tracepoints

This patch adds the resource name to dlm tracepoints. The name
usually comes through the lkb_resource, but in some cases a resource
may not yet be associated with an lkb, in which case the name and
namelen parameters are used.

It should be okay to access the lkb_resource and the res_name field at
the time when the tracepoint is invoked. The resource is assigned to a
lkb and it's reference is being held during the tracepoint call. During
this time the resource cannot be freed. Also a lkb will never switch
its assigned resource. The name of a dlm_rsb is assigned at creation
time and should never be changed during runtime as well.

The TP_printk() call uses always a hexadecimal string array
representation for the resource name (which is not necessarily ascii.)

Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
/linux/fs/dlm/
H A Dlock.cdiff 5d92a30e900dc97221e36f09ae740457d560d281 Wed Jun 22 20:45:12 CEST 2022 Alexander Aring <aahringo@redhat.com> fs: dlm: add resource name to tracepoints

This patch adds the resource name to dlm tracepoints. The name
usually comes through the lkb_resource, but in some cases a resource
may not yet be associated with an lkb, in which case the name and
namelen parameters are used.

It should be okay to access the lkb_resource and the res_name field at
the time when the tracepoint is invoked. The resource is assigned to a
lkb and it's reference is being held during the tracepoint call. During
this time the resource cannot be freed. Also a lkb will never switch
its assigned resource. The name of a dlm_rsb is assigned at creation
time and should never be changed during runtime as well.

The TP_printk() call uses always a hexadecimal string array
representation for the resource name (which is not necessarily ascii.)

Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>