Thomas Gleixner 3f804f6d20 KVM: x86: Prevent deadlock against tk_core.seq ... syzbot reported a possible deadlock in pvclock_gtod_notify(): CPU 0 CPU 1 write_seqcount_begin(&tk_core.seq); pvclock_gtod_notify() spin_lock(&pool->lock); queue_work(..., &pvclock_gtod_work) ktime_get() spin_lock(&pool->lock); do { seq = read_seqcount_begin(tk_core.seq) ... } while (read_seqcount_retry(&tk_core.seq, seq); While this is unlikely to happen, it's possible. Delegate queue_work() to irq_work() which postpones it until the tk_core.seq write held region is left and interrupts are reenabled. Fixes: 16e8d74d2d ("KVM: x86: notifier for clocksource changes") Reported-by: syzbot+6beae4000559d41d80f8@syzkaller.appspotmail.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Message-Id: <87h7jgm1zy.ffs@nanos.tec.linutronix.de> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2021-05-07 06:06:21 -04:00
..
alpha
arc
arm
arm64
csky
h8300
hexagon
ia64
m68k
microblaze
mips
nds32
nios2
openrisc
parisc
powerpc	KVM: PPC: Book3S HV: Fix conversion to gfn-based MMU notifier callbacks	2021-05-07 06:06:20 -04:00
riscv
s390
sh
sparc
um
x86	KVM: x86: Prevent deadlock against tk_core.seq	2021-05-07 06:06:21 -04:00
xtensa
.gitignore
Kconfig