[tip: locking/urgent] locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

2021-04-17 Thread tip-bot2 for Ali Saidi
The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896 Gitweb: https://git.kernel.org/tip/84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896 Author:Ali Saidi AuthorDate:Thu, 15 Apr 2021 17:27:11 Committer

[PATCH v2] locking/qrwlock: Fix ordering in queued_write_lock_slowpath

2021-04-15 Thread Ali Saidi
his issue at which point the atomic_cond_read can be switched to use relaxed semantics. Fixes: b519b56e378ee ("locking/qrwlock: Use atomic_cond_read_acquire() when spinning in qrwlock") Signed-off-by: Ali Saidi Cc: sta...@vger.kernel.org Acked-by: Will Deacon Tested-by: Steve Cappe

Re: [PATCH] locking/qrwlock: Fix ordering in queued_write_lock_slowpath

2021-04-15 Thread Ali Saidi
On Thu, 15 Apr 2021 16:02:29 +0100, Will Deacon wrote: > On Thu, Apr 15, 2021 at 02:25:52PM +0000, Ali Saidi wrote: > > While this code is executed with the wait_lock held, a reader can > > acquire the lock without holding wait_lock. The writer side loops > &g

[PATCH] locking/qrwlock: Fix ordering in queued_write_lock_slowpath

2021-04-15 Thread Ali Saidi
when spinning in qrwloc") Signed-off-by: Ali Saidi Cc: sta...@vger.kernel.org --- kernel/locking/qrwlock.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/locking/qrwlock.c b/kernel/locking/qrwlock.c index 4786dd271b45..10770f6ac4d9 100644 --- a/kernel/locking/qrwlo

[PATCH] irqchip/gic-v3-its: Don't try to move a disabled irq

2020-05-28 Thread Ali Saidi
and change the activate code to try and use the previous affinity. Signed-off-by: Ali Saidi --- drivers/irqchip/irq-gic-v3-its.c | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c index 124251b0ccba

[PATCH 1/2] arm64/mmap: handle worst-case heap randomization in mmap_base

2019-03-12 Thread Ali Saidi
lead to the stack and heap being arbitrarily close to each other. Signed-off-by: Ali Saidi --- arch/arm64/mm/mmap.c | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm64/mm/mmap.c b/arch/arm64/mm/mmap.c index 842c8a5fcd53..0778f7ba8306 100644 --- a/arch/arm64/mm/mmap.c +++ b/arch

[PATCH 0/2] handle worst-case heap randomization in mmap_base

2019-03-12 Thread Ali Saidi
lead to the stack and heap being arbitrarily close to each other. Ali Saidi (2): arm64/mmap: handle worst-case heap randomization in mmap_base x86/mmap: handle worst-case heap randomization in mmap_base arch/arm64/mm/mmap.c | 8 arch/x86/mm/mmap.c | 4 2 files changed, 12

[PATCH 2/2] x86/mmap: handle worst-case heap randomization in mmap_base

2019-03-12 Thread Ali Saidi
lead to the stack and heap being arbitrarily close to each other. Signed-off-by: Ali Saidi --- arch/x86/mm/mmap.c | 4 1 file changed, 4 insertions(+) diff --git a/arch/x86/mm/mmap.c b/arch/x86/mm/mmap.c index db3165714521..98a2875c37e3 100644 --- a/arch/x86/mm/mmap.c +++ b/arch/x86/mm/mmap.c