> I think UBSAN has correctly identified a bug. I looked at the code in
> v4.6. In file arch/x86/events/core.c, in the function
> filter_events(), there is a loop starting at line 1554 that should go
> over 10 event counters. But in file arch/x86/events/intel/p6.c, only
> 8 event counters have
> I think UBSAN has correctly identified a bug. I looked at the code in
> v4.6. In file arch/x86/events/core.c, in the function
> filter_events(), there is a loop starting at line 1554 that should go
> over 10 event counters. But in file arch/x86/events/intel/p6.c, only
> 8 event counters have
0.150000] UBSAN: Undefined behaviour in arch/x86/events/intel/p6.c:115:29
> [0.15] index 8 is out of range for type 'u64 [8]'
> [0.15] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.6.0 #21
> [0.15] Hardware name: Dell Computer Corporation PowerEdge 1550/933
&
rom UBSAN but I do not have any
> amd machines from that time frame online for now, so p6 only.
>
> [0.15] Performance Events: p6 PMU driver.
> [0.15]
> ====
> [0.150000] UBSAN: Undef
online for now, so p6 only.
[0.15] Performance Events: p6 PMU driver.
[0.15]
[0.15] UBSAN: Undefined behaviour in arch/x86/events/intel/p6.c:115:29
[0.15] index 8 is out of range for type
online for now, so p6 only.
[0.15] Performance Events: p6 PMU driver.
[0.15]
[0.15] UBSAN: Undefined behaviour in arch/x86/events/intel/p6.c:115:29
[0.15] index 8 is out of range for type
6 matches
Mail list logo
