linux-kernel - Re: linux acpi (thunderbolt? bug)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1802141306360.1292@nanos.tec.linutronix.de>
Date:   Wed, 14 Feb 2018 13:09:10 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Yuriy Vostrikov <delamonpansie@...il.com>
cc:     linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: linux acpi (thunderbolt? bug)

On Wed, 14 Feb 2018, Yuriy Vostrikov wrote:
> after boot
> name:   VECTOR
>  size:   0
>  mapped: 64
>  flags:  0x00000041
> Online bitmaps:        2
> Global available:    368
> Global reserved:      26
> Total allocated:      38
> System: 41: 0-19,32,50,128,238-255
>  | CPU | avl | man | act | vectors
>      0   184     1    19  33-49,51-52
>      1   184     1    19  33-49,51-52
> 
> after unplug
> name:   VECTOR
>  size:   0
>  mapped: 55
>  flags:  0x00000041
> Online bitmaps:        2
> Global available:    377
> Global reserved:      26
> Total allocated:      29
> System: 41: 0-19,32,50,128,238-255
>  | CPU | avl | man | act | vectors
>      0   188     1    15  33-46,48
>      1   189     1    14  33-46
> 
> after sleep 1 time
> name:   VECTOR
>  size:   0
>  mapped: 35
>  flags:  0x00000041
> Online bitmaps:        2
> Global available:    385
> Global reserved:      12
> Total allocated:      32
> System: 41: 0-19,32,50,128,238-255
>  | CPU | avl | man | act | vectors
>      0   185     1    18  33-43,46-49,51-53
>      1   200     1     3  33-37

The accounting is already screwed. CPU1 claims to have 3 allocated vectors,
but the allocation bitmap has 5 bits set !?! 

I have no idea yet how that can happen. Lemme stare into the code some more
and I came back to you.

Thanks,

	tglx