From: Lee Jones <lee.jones@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: futex breakage in 4.9 stable branch
Date: Mon, 1 Mar 2021 08:35:49 +0000 [thread overview]
Message-ID: <20210301083549.GF641347@dell> (raw)
In-Reply-To: <YDygp3WYafzcgt+s@kroah.com>
On Mon, 01 Mar 2021, Greg Kroah-Hartman wrote:
> On Mon, Mar 01, 2021 at 01:13:08AM +0100, Ben Hutchings wrote:
> > On Tue, 2021-02-23 at 15:00 +0100, Greg Kroah-Hartman wrote:
> > > I'm announcing the release of the 4.9.258 kernel.
> > >
> > > All users of the 4.9 kernel series must upgrade.
> > >
> > > The updated 4.9.y git tree can be found at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y
> > > and can be browsed at the normal kernel.org git web browser:
> > >
> >
> > The backported futex fixes are still incomplete/broken in this version.
> > If I enable lockdep and run the futex self-tests (from 5.10):
> >
> > - on 4.9.246, they pass with no lockdep output
> > - on 4.9.257 and 4.9.258, they pass but futex_requeue_pi trigers a
> > lockdep splat
> >
> > I have a local branch that essentially updates futex and rtmutex in
> > 4.9-stable to match 4.14-stable. With this, the tests pass and lockdep
> > is happy.
> >
> > Unfortunately, that branch has about another 60 commits. Further, the
> > more we change futex in 4.9, the more difficult it is going to be to
> > update the 4.9-rt branch. But I don't see any better option available
> > at the moment.
> >
> > Thoughts?
>
> There were some posted futex fixes for 4.9 (and 4.4) on the stable list
> that I have not gotten to yet.
>
> Hopefully after these are merged (this week), these issues will be
> resolved.
>
> If not, then yes, they need to be fixed and any help you can provide
> would be appreciated.
>
> As for "difficulty", yes, it's rough, but the changes backported were
> required, for obvious reasons :(
Apologies for the fuss.
The back-port become more complex the further back it was taken..
Had I known about the self-tests, I would have ensured those were
passing too, as well as the the build/boot/auto-builder tests
actually carried out.
Let me know if there's anything further I can do to help.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-03-01 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 14:00 Linux 4.9.258 Greg Kroah-Hartman
2021-02-23 14:00 ` Greg Kroah-Hartman
2021-03-01 0:13 ` futex breakage in 4.9 stable branch Ben Hutchings
2021-03-01 8:07 ` Greg Kroah-Hartman
2021-03-01 8:35 ` Lee Jones [this message]
2021-03-01 17:29 ` Ben Hutchings
2021-03-04 9:12 ` Mike Galbraith
2021-03-04 13:11 ` Greg Kroah-Hartman
2021-03-04 13:23 ` Mike Galbraith
2021-03-04 18:47 ` Thomas Gleixner
2021-03-05 6:41 ` Mike Galbraith
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=20210301083549.GF641347@dell \
--to=lee.jones@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.