From: Greg KH <gregkh@linuxfoundation.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Subject: Re: backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e
Date: Mon, 10 Oct 2022 21:08:02 +0200 [thread overview]
Message-ID: <Y0Rtkk7hA4CBwp16@kroah.com> (raw)
In-Reply-To: <Yz21dn2vJPOVOffr@kroah.com>
On Wed, Oct 05, 2022 at 06:48:54PM +0200, Greg KH wrote:
> On Mon, Oct 03, 2022 at 08:28:06AM -0400, Mikulas Patocka wrote:
> >
> >
> > On Sat, 1 Oct 2022, Greg KH wrote:
> >
> > > On Fri, Sep 30, 2022 at 11:32:30AM -0400, Mikulas Patocka wrote:
> > > > Hi
> > > >
> > > > Here I'm submitting backport of patches
> > > > 8238b4579866b7c1bb99883cfe102a43db5506ff and
> > > > d6ffe6067a54972564552ea45d320fb98db1ac5e to the stable branches.
> > >
> > > Thanks, but you provide no information as to why these are needed.
> > >
> > > What needs them? They are just adding new functions to the tree from
> > > what I can tell.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > There's a race condition in wait_on_bit. wait_on_bit tests a bit using the
> > "test_bit" function, however this function doesn't do any memory barrier,
> > so the memory accesses that follow wait_on_bit may be reordered before it
> > and return invalid data.
> >
> > Linus didn't want to add a memory barrier to wait_on_bit, he instead
> > wanted to introduce a new function test_bit_acquire that performs the
> > "acquire" memory barrier and use it in wait_on_bit.
> >
> > The patch d6ffe6067a54972564552ea45d320fb98db1ac5e fixes an oversight in
> > the patch 8238b4579866b7c1bb99883cfe102a43db5506ff where the function
> > test_bit_acquire was not defined for some architectures and this caused
> > compile failure.
> >
> > The backport of the patch 8238b4579866b7c1bb99883cfe102a43db5506ff should
> > be applied first and the backport of the patch
> > d6ffe6067a54972564552ea45d320fb98db1ac5e afterwards.
>
> All now queued up, thanks.
Nope, these cause loads of breakages. See
https://lore.kernel.org/r/09eca44e-4d91-a060-d48c-d0aa41ac5045@roeck-us.net
for one such example, and I know kbuild sent you other build problems.
I'll drop all of these from the stable trees now. Please feel free to
resend them when you have the build issues worked out.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-10 19:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 15:32 backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Mikulas Patocka
2022-09-30 15:33 ` [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-09-30 15:33 ` Mikulas Patocka
2022-09-30 15:34 ` Mikulas Patocka
2022-09-30 15:34 ` Mikulas Patocka
2022-09-30 15:34 ` Mikulas Patocka
2022-10-01 7:01 ` Greg KH
2022-09-30 15:35 ` [PATCH] provide arch_test_bit_acquire for architectures that define test_bit Mikulas Patocka
2022-09-30 15:35 ` Mikulas Patocka
2022-09-30 15:36 ` Mikulas Patocka
2022-09-30 15:36 ` Mikulas Patocka
2022-09-30 15:36 ` Mikulas Patocka
2022-10-01 7:00 ` Greg KH
2022-10-01 6:59 ` backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Greg KH
2022-10-03 12:28 ` Mikulas Patocka
2022-10-03 12:28 ` [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-10-03 12:29 ` Mikulas Patocka
2022-10-03 12:29 ` Mikulas Patocka
2022-10-03 12:29 ` Mikulas Patocka
2022-10-03 12:30 ` Mikulas Patocka
2022-10-03 12:30 ` [PATCH] provide arch_test_bit_acquire for architectures that define test_bit Mikulas Patocka
2022-10-03 12:31 ` Mikulas Patocka
2022-10-03 12:31 ` Mikulas Patocka
2022-10-03 12:31 ` Mikulas Patocka
2022-10-03 12:32 ` Mikulas Patocka
2022-10-05 16:48 ` backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Greg KH
2022-10-10 19:08 ` Greg KH [this message]
2022-10-11 9:48 ` Mikulas Patocka
2022-10-11 9:58 ` Greg KH
2022-10-18 11:36 ` Mikulas Patocka
2022-10-18 11:37 ` [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-10-18 11:37 ` Mikulas Patocka
2022-10-18 11:38 ` Mikulas Patocka
2022-10-18 11:38 ` Mikulas Patocka
2022-10-18 11:39 ` Mikulas Patocka
2022-10-18 11:39 ` Mikulas Patocka
2022-10-18 11:39 ` Mikulas Patocka
2022-10-26 17:01 ` backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e Greg KH
2022-10-27 11:45 ` Mikulas Patocka
2022-10-27 11:53 ` Greg KH
2022-10-27 12:48 ` Mikulas Patocka
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=Y0Rtkk7hA4CBwp16@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mpatocka@redhat.com \
--cc=stable@vger.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