From: mwjian@foxmail.com (马文健)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: spinlock: avoid exclusive accesses on unlock() path
Date: Tue, 7 Aug 2018 09:59:13 +0800 [thread overview]
Message-ID: <tencent_7ECB5CA838202151603A2FF6@qq.com> (raw)
In-Reply-To: <tencent_6BF9DD7B77B1CAA95FBAEE73@qq.com>
Hi
while one cpu is doing arch_spin_unlock,another cpu doing arch_spin_lock
the first cpu's
lock->tickets.owner++;
may be over writed by the second's
strex %2, %1, [%3]\n
so the owner filed doesn't get increased.
But i'm not sure about this, may be there are something i have missed.
Thanks.
------------------ Original ------------------
next parent reply other threads:[~2018-08-07 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_76D135D5D379BDAB2A2436393315C6E4E807@qq.com>
[not found] ` <tencent_6BF9DD7B77B1CAA95FBAEE73@qq.com>
2018-08-07 1:59 ` 马文健 [this message]
2018-08-07 16:56 ` [PATCH] ARM: spinlock: avoid exclusive accesses on unlock() path Will Deacon
[not found] <tencent_5E0B19C04FA531B834205F9F@qq.com>
2018-08-08 15:44 ` [PATCH] ARM: spinlock: avoid exclusive accesses on unlock()path Will Deacon
2013-01-11 15:07 [PATCH] ARM: spinlock: avoid exclusive accesses on unlock() path Will Deacon
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=tencent_7ECB5CA838202151603A2FF6@qq.com \
--to=mwjian@foxmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).