BMC/Intel-BMC/linux.git/include/trace/events, branch dev-5.3

Merge tag 'v5.3.15' into dev-5.3

2019-12-11T22:32:06+00:00

This is the 5.3.15 stable release Signed-off-by: Joel Stanley

tcp: remove redundant new line from tcp_event_sk_skb

2019-11-20T15:49:00+00:00

[ Upstream commit dd3d792def0d4f33bbf319982b1878b0c8aaca34 ] This removes '\n' from trace event class tcp_event_sk_skb to avoid redundant new blank line and make output compact. Fixes: af4325ecc24f ("tcp: expose sk_state in tcp_retransmit_skb tracepoint") Reviewed-by: Eric Dumazet Reviewed-by: Yafang Shao Signed-off-by: Tony Lu Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman

Merge tag 'v5.3.10' into dev-5.3

2019-11-11T01:17:54+00:00

This is the 5.3.10 stable release Signed-off-by: Joel Stanley

rxrpc: Fix trace-after-put looking at the put peer record

2019-11-06T12:09:27+00:00

commit 55f6c98e3674ce16038a1949c3f9ca5a9a99f289 upstream. rxrpc_put_peer() calls trace_rxrpc_peer() after it has done the decrement of the refcount - which looks at the debug_id in the peer record. But unless the refcount was reduced to zero, we no longer have the right to look in the record and, indeed, it may be deleted by some other thread. Fix this by getting the debug_id out before decrementing the refcount and then passing that into the tracepoint. This can cause the following symptoms: BUG: KASAN: use-after-free in __rxrpc_put_peer net/rxrpc/peer_object.c:411 [inline] BUG: KASAN: use-after-free in rxrpc_put_peer+0x685/0x6a0 net/rxrpc/peer_object.c:435 Read of size 8 at addr ffff888097ec0058 by task syz-executor823/24216 Fixes: 1159d4b496f5 ("rxrpc: Add a tracepoint to track rxrpc_peer refcounting") Reported-by: syzbot+b9be979c55f2bea8ed30@syzkaller.appspotmail.com Signed-off-by: David Howells Signed-off-by: Greg Kroah-Hartman

trace: fsi: Print transfer size unsigned

2019-11-04T04:07:31+00:00

Due to other bugs I observed a spurious -1 transfer size. OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery Signed-off-by: Joel Stanley

Merge tag 'v5.3.8' into dev-5.3

2019-10-30T15:00:42+00:00

This is the 5.3.8 stable release Signed-off-by: Joel Stanley

btrfs: tracepoints: Fix bad entry members of qgroup events

2019-10-29T08:22:45+00:00

commit 1b2442b4ae0f234daeadd90e153b466332c466d8 upstream. [BUG] For btrfs:qgroup_meta_reserve event, the trace event can output garbage: qgroup_meta_reserve: 9c7f6acc-b342-4037-bc47-7f6e4d2232d7: refroot=5(FS_TREE) type=DATA diff=2 qgroup_meta_reserve: 9c7f6acc-b342-4037-bc47-7f6e4d2232d7: refroot=5(FS_TREE) type=0x258792 diff=2 The @type can be completely garbage, as DATA type is not possible for trace_qgroup_meta_reserve() trace event. [CAUSE] Ther are several problems related to qgroup trace events: - Unassigned entry member Member entry::type of trace_qgroup_update_reserve() and trace_qgourp_meta_reserve() is not assigned - Redundant entry member Member entry::type is completely useless in trace_qgroup_meta_convert() Fixes: 4ee0d8832c2e ("btrfs: qgroup: Update trace events for metadata reservation") CC: stable@vger.kernel.org # 4.10+ Reviewed-by: Nikolay Borisov Signed-off-by: Qu Wenruo Reviewed-by: David Sterba Signed-off-by: David Sterba Signed-off-by: Greg Kroah-Hartman

fsi: aspeed: Add trace when error occurs

2019-10-16T04:07:45+00:00

This prints out three registers in the FSI master when an error occurs. OpenBMC-Staging-Count: 1 Reviewed-by: Andrew Jeffery Signed-off-by: Joel Stanley

fsi: aspeed: Remove base from trace

2019-10-16T04:07:42+00:00

The base was showing the virtual address of the FSI master, which was not useful for most users of the tracepoint. OpenBMC-Staging-Count: 1 Reviewed-by: Eddie James Tested-by: Eddie James Acked-by: Andrew Jeffery Signed-off-by: Joel Stanley

Merge tag 'v5.3.6' into dev-5.3

2019-10-14T01:24:00+00:00

This is the 5.3.6 stable release