From: Salvatore Bonaccorso <carnil@debian.org>
To: martin-eric.racine@iki.fi, 1017425@bugs.debian.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ben Hutchings <ben@decadent.org.uk>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, regressions@lists.linux.dev,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Subject: Re: Bug#1017425: [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it
Date: Tue, 30 Aug 2022 15:35:27 +0200 [thread overview]
Message-ID: <Yw4SH2EuvnFJZHJs@lorien.valinor.li> (raw)
In-Reply-To: <CAPZXPQfrCQi5y0yS0kXNYajb_YyRGBPj1hhJEYEWWUsJxa-EHw@mail.gmail.com>
Hi Martin,
On Tue, Aug 30, 2022 at 03:18:51PM +0300, Martin-??ric Racine wrote:
> On Tue, Aug 30, 2022 at 3:00 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > On Tue, Aug 30, 2022 at 02:42:04PM +0300, Martin-??ric Racine wrote:
> > > On Fri, Aug 19, 2022 at 3:15 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > > >
> > > > On Fri, Aug 19, 2022 at 01:38:27PM +0200, Ben Hutchings wrote:
> > > >
> > > > > So that puts the whole __FILL_RETURN_BUFFER inside an alternative, and
> > > > > we can't have nested alternatives. That's unfortunate.
> > > >
> > > > Well, both alternatives end with the LFENCE instruction, so I could pull
> > > > it out and do two consequtive ALTs, but unrolling the loop for i386 is
> > > > a better solution in that the sequence, while larger, removes the need
> > > > for the LFENCE.
> > >
> > > Have we reached a definitive conclusion on to how to fix this?
> >
> > https://git.kernel.org/tip/332924973725e8cdcc783c175f68cf7e162cb9e5
>
> Thanks.
>
> Ben: When can we expect an updated kernel to security-updates at Debian?
When the update is ready to go. Likely the update for the next point
release for bullseye will contain the fix for this issue.
Regards,
Salvatore
next prev parent reply other threads:[~2022-08-30 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 0:33 [PATCH] x86/speculation: Avoid LFENCE in FILL_RETURN_BUFFER on CPUs that lack it Ben Hutchings
2022-08-19 8:47 ` Peter Zijlstra
2022-08-19 11:01 ` Peter Zijlstra
2022-08-19 11:33 ` Martin-Éric Racine
2022-08-19 11:38 ` Ben Hutchings
2022-08-19 12:15 ` Peter Zijlstra
2022-08-30 11:42 ` Martin-Éric Racine
2022-08-30 12:00 ` Peter Zijlstra
2022-08-30 12:18 ` Martin-Éric Racine
2022-08-30 13:35 ` Salvatore Bonaccorso [this message]
2022-08-19 11:02 ` Ben Hutchings
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=Yw4SH2EuvnFJZHJs@lorien.valinor.li \
--to=carnil@debian.org \
--cc=1017425@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=daniel.sneddon@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin-eric.racine@iki.fi \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=x86@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