summaryrefslogtreecommitdiff
path: root/include/linux/bitmap.h
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@redhat.com>2025-01-07 17:27:17 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-01-23 17:22:57 +0100
commit621f95fa0b93ce93a4b2f2d9277d0e8d88833776 (patch)
tree6b2d83c55c5d6f502ec2188c4cea6a8471d81347 /include/linux/bitmap.h
parent22be1d90a6211c88dd093b25d1f3aa974d0d9f9d (diff)
downloadlinux-621f95fa0b93ce93a4b2f2d9277d0e8d88833776.tar.gz
linux-621f95fa0b93ce93a4b2f2d9277d0e8d88833776.tar.bz2
linux-621f95fa0b93ce93a4b2f2d9277d0e8d88833776.zip
poll_wait: add mb() to fix theoretical race between waitqueue_active() and .poll()
[ Upstream commit cacd9ae4bf801ff4125d8961bb9a3ba955e51680 ] As the comment above waitqueue_active() explains, it can only be used if both waker and waiter have mb()'s that pair with each other. However __pollwait() is broken in this respect. This is not pipe-specific, but let's look at pipe_poll() for example: poll_wait(...); // -> __pollwait() -> add_wait_queue() LOAD(pipe->head); LOAD(pipe->head); In theory these LOAD()'s can leak into the critical section inside add_wait_queue() and can happen before list_add(entry, wq_head), in this case pipe_poll() can race with wakeup_pipe_readers/writers which do smp_mb(); if (waitqueue_active(wq_head)) wake_up_interruptible(wq_head); There are more __pollwait()-like functions (grep init_poll_funcptr), and it seems that at least ep_ptable_queue_proc() has the same problem, so the patch adds smp_mb() into poll_wait(). Link: https://lore.kernel.org/all/20250102163320.GA17691@redhat.com/ Signed-off-by: Oleg Nesterov <oleg@redhat.com> Link: https://lore.kernel.org/r/20250107162717.GA18922@redhat.com Signed-off-by: Christian Brauner <brauner@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/linux/bitmap.h')
0 files changed, 0 insertions, 0 deletions