From: Waiman Long <llong@redhat.com>
To: Ali Saidi <alisaidi@amazon.com>, linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, steve.capper@arm.com,
benh@kernel.crashing.org, stable@vger.kernel.org,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Boqun Feng <boqun.feng@gmail.com>
Subject: Re: [PATCH v2] locking/qrwlock: Fix ordering in queued_write_lock_slowpath
Date: Thu, 15 Apr 2021 13:45:54 -0400 [thread overview]
Message-ID: <e9dfb6c2-3efc-5f4c-ebba-2f26f14295d5@redhat.com> (raw)
In-Reply-To: <20210415172711.15480-1-alisaidi@amazon.com>
On 4/15/21 1:27 PM, 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
> checking the value with the atomic_cond_read_acquire(), but only truly
> acquires the lock when the compare-and-exchange is completed
> successfully which isn’t ordered. This exposes the window between the
> acquire and the cmpxchg to an A-B-A problem which allows reads following
> the lock acquisition to observe values speculatively before the write
> lock is truly acquired.
>
> We've seen a problem in epoll where the reader does a xchg while
> holding the read lock, but the writer can see a value change out from under it.
>
> Writer | Reader 2
> --------------------------------------------------------------------------------
> ep_scan_ready_list() |
> |- write_lock_irq() |
> |- queued_write_lock_slowpath() |
> |- atomic_cond_read_acquire() |
> | read_lock_irqsave(&ep->lock, flags);
> --> (observes value before unlock)| chain_epi_lockless()
> | | epi->next = xchg(&ep->ovflist, epi);
> | | read_unlock_irqrestore(&ep->lock, flags);
> | |
> | atomic_cmpxchg_relaxed() |
> |-- READ_ONCE(ep->ovflist); |
>
> A core can order the read of the ovflist ahead of the
> atomic_cmpxchg_relaxed(). Switching the cmpxchg to use acquire semantics
> addresses this 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 <alisaidi@amazon.com>
> Cc: stable@vger.kernel.org
> Acked-by: Will Deacon <will@kernel.org>
> Tested-by: Steve Capper <steve.capper@arm.com>
> Reviewed-by: Steve Capper <steve.capper@arm.com>
>
> ---
> 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/qrwlock.c
> +++ b/kernel/locking/qrwlock.c
> @@ -73,8 +73,8 @@ void queued_write_lock_slowpath(struct qrwlock *lock)
>
> /* When no more readers or writers, set the locked flag */
> do {
> - atomic_cond_read_acquire(&lock->cnts, VAL == _QW_WAITING);
> - } while (atomic_cmpxchg_relaxed(&lock->cnts, _QW_WAITING,
> + atomic_cond_read_relaxed(&lock->cnts, VAL == _QW_WAITING);
> + } while (atomic_cmpxchg_acquire(&lock->cnts, _QW_WAITING,
> _QW_LOCKED) != _QW_WAITING);
> unlock:
> arch_spin_unlock(&lock->wait_lock);
Acked-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2021-04-15 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 17:27 Ali Saidi
2021-04-15 17:45 ` Waiman Long [this message]
2021-04-16 16:52 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e9dfb6c2-3efc-5f4c-ebba-2f26f14295d5@redhat.com \
--to=llong@redhat.com \
--cc=alisaidi@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=steve.capper@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®