Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Hector Martin <marcan@marcan.st>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: tj@kernel.org, will@kernel.org, peterz@infradead.org,
	jirislaby@kernel.org, maz@kernel.org, mark.rutland@arm.com,
	boqun.feng@gmail.com, catalin.marinas@arm.com, oneukum@suse.com,
	roman.penyaev@profitbricks.com, asahi@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, marcan@marcan.st,
	stable@vger.kernel.org
Subject: Re: [PATCH] workqueue: Fix memory ordering race in queue_work*()
Date: Tue, 16 Aug 2022 12:14:55 +0800	[thread overview]
Message-ID: <YvsZvwxACuGw3KIt@gondor.apana.org.au> (raw)
In-Reply-To: <20220815175810.17780-1-marcan@marcan.st>

Hector Martin <marcan@marcan.st> wrote:
>
> This has been broken since the dawn of time, and it was incompletely
> fixed by 346c09f80459, which added the necessary barriers in the work
> execution path but failed to account for the missing barrier in the
> test_and_set_bit() failure case. Fix it by switching to
> atomic_long_fetch_or(), which does have unconditional barrier semantics
> regardless of whether the bit was already set or not (this is actually
> just test_and_set_bit() minus the early exit path).

test_and_set_bit is supposed to contain a full memory barrier.
If it doesn't then your arch is broken and needs to be fixed.

Changing this one spot is pointless because such assumptions
are all over the kernel.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-08-16  4:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 17:58 [PATCH] workqueue: Fix memory ordering race in queue_work*() Hector Martin
2022-08-15 19:10 ` Tejun Heo
2022-08-16  4:15   ` Herbert Xu
2022-08-16  5:27     ` Linus Torvalds
2022-08-16  5:36       ` Hector Martin
2022-08-16  5:52         ` Linus Torvalds
2022-08-16  6:28           ` Hector Martin
2022-08-16  7:48             ` Herbert Xu
2022-08-16  8:01               ` Hector Martin
2022-08-16  5:48       ` Herbert Xu
2022-08-16  6:03         ` Linus Torvalds
2022-08-16 13:41       ` Will Deacon
2022-08-16 14:55         ` Boqun Feng
2022-08-16 16:22           ` Hector Martin
2022-08-16 16:43             ` Boqun Feng
2022-08-16 16:58             ` Linus Torvalds
2022-08-16 16:41         ` Linus Torvalds
2022-08-17  5:05           ` Herbert Xu
2022-08-16 17:01         ` Tejun Heo
2022-08-16 16:26     ` Tejun Heo
2022-08-16 17:21       ` Hector Martin
2022-08-16  4:14 ` Herbert Xu [this message]
2022-08-16  5:37   ` Hector Martin

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=YvsZvwxACuGw3KIt@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=asahi@lists.linux.dev \
    --cc=boqun.feng@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=oneukum@suse.com \
    --cc=peterz@infradead.org \
    --cc=roman.penyaev@profitbricks.com \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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