summaryrefslogtreecommitdiff
path: root/ifpps/.gitignore
blob: 32aad4d4537ef26d0c36abbff8d7e36d246f1a91 (plain)
1
2
3
4
*.*

!.gitignore
!Makefile
rl'>
authorLinus Torvalds <torvalds@linux-foundation.org>2016-06-13 19:54:46 -1000
committerLinus Torvalds <torvalds@linux-foundation.org>2016-06-13 19:54:46 -1000
commitdb06d759d6cf903aeda8c107fd3abd366dd80200 (patch)
tree6e9ddea15240dcba9dff738a345297e982ae9324
parent35398ee3f00a4363faa1bd0fe7bb6a90f8a6b7e4 (diff)
parent6710e594f71ccaad8101bc64321152af7cd9ea28 (diff)
Merge branch 'for-4.7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu
Pull percpu fixes from Tejun Heo: "While adding GFP_ATOMIC support to the percpu allocator, the synchronization for the fast-path which doesn't require external allocations was separated into pcpu_lock. Unfortunately, it incorrectly decoupled async paths and percpu chunks could get destroyed while still being operated on. This contains two patches to fix the bug" * 'for-4.7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu: percpu: fix synchronization between synchronous map extension and chunk destruction percpu: fix synchronization between chunk->map_extend_work and chunk destruction
Diffstat
metric
The recent commit which prevents double activation of interrupts unearthed interesting code in x86. The code (ab)uses irq_domain_activate_irq() to reconfigure an already activated interrupt. That trips over the prevention code now. Fix it by deactivating the interrupt before activating the new configuration. Fixes: 08d85f3ea99f1 "irqdomain: Avoid activating interrupts more than once" Reported-and-tested-by: Mike Galbraith <efault@gmx.de> Reported-and-tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Andrey Ryabinin <aryabinin@virtuozzo.com> Cc: Marc Zyngier <marc.zyngier@arm.com> Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701311901580.3457@nanos
Diffstat (limited to 'net/ceph/auth_x.c')