From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: Ulrich Hecht <uli@fpond.eu>, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] 4.4 backports -- x86 speculation
Date: Tue, 14 Jun 2022 13:10:24 +0200 [thread overview]
Message-ID: <20220614111024.GC20387@duo.ucw.cz> (raw)
In-Reply-To: <16F8778C49247DE6.18003@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 3207 bytes --]
Hi!
> > > 0001-ptrace-Check-PTRACE_O_SUSPEND_SECCOMP-permission-on-.patch
> > > 0002-xen-blkfront-don-t-use-gnttab_query_foreign_access-f.patch
> > > 0003-x86-modpost-Replace-last-remnants-of-RETPOLINE-with-.patch
> > >
> > > I already had these from the last round.
> > >
> > > 0004-arm-arm64-smccc-psci-add-arm_smccc_1_1_get_conduit.patch
> > >
> > > I'll take this, but I'll need to recheck the context.
> > >
> > > 0005-x86-speculation-Add-RETPOLINE_AMD-support-to-the-inl.patch
> > > 0006-x86-retpoline-Make-CONFIG_RETPOLINE-depend-on-compil.patch
> > > 0007-x86-retpoline-Remove-minimal-retpoline-support.patch
> > > 0008-Documentation-Add-section-about-CPU-vulnerabilities-.patch
> > > 0009-Documentation-Add-swapgs-description-to-the-Spectre-.patch
> > > 0010-Documentation-refer-to-config-RANDOMIZE_BASE-for-ker.patch
> > > 0011-x86-speculation-Rename-RETPOLINE_AMD-to-RETPOLINE_LF.patch
> > > 0012-x86-speculation-Add-eIBRS-Retpoline-options.patch
> > > 0013-Documentation-hw-vuln-Update-spectre-doc.patch
> > > 0014-x86-speculation-Include-unprivileged-eBPF-status-in-.patch
> > > 0015-x86-speculation-Use-generic-retpoline-by-default-on-.patch
> > > 0016-x86-speculation-Update-link-to-AMD-speculation-white.patch
> > > 0017-x86-speculation-Warn-about-Spectre-v2-LFENCE-mitigat.patch
> > > 0018-x86-speculation-Warn-about-eIBRS-LFENCE-Unprivileged.patch
> > >
> > > Applied to -st-rc branch. Let me attempt to do some basic testing.
> >
> > With all the patches applied, I get this:
>
> My tree currently looks like this:
>
> 882867c873bbf048cd3574a3fda18742726839b8 x86/retpoline: Remove minimal retpoline support
> 5a5cafcebb8d249808b0bd63ca75642e5e1ec821 x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support
> 64bdd7860d908641beb8c2aceeb34b4ddd773024 x86/speculation: Add RETPOLINE_AMD support to the inline asm CALL_NOSPEC variant
> 41f63e3d55265f90c76a00412252a34cd3f0142e arm/arm64: smccc/psci: add arm_smccc_1_1_get_conduit()
> b45151ba21854b8b38897696e163b04a7b09e204 x86, modpost: Replace last remnants of RETPOLINE with CONFIG_RETPOLINE
> 728dc418dd6a8f3ce99f306ef52e6286aa6e13d9 xen/blkfront: don't use gnttab_query_foreign_access() for mapped status
> 10e10492a0474d9b57558f67cae41d2d7d7d11cf ptrace: Check PTRACE_O_SUSPEND_SECCOMP permission on PTRACE_SEIZE
> 67f46bb7179f10425f9fbf81faa81c05c1d810f4 add needed testing
> 5cd6adc62818c613bef3fdcf48d5c1473e617e9f (origin/linux-4.4.y-st, linux-4.4.y-st) Merge changes from 4.9.314.
>
> Testing 64bdd786, that one fails, testing 41f63e3d5: that one does not
> fail in the same
> way. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/563276264.
>
> So it looks like 64bdd7860d908641beb8c2aceeb34b4ddd773024
> x86/speculation: Add RETPOLINE_AMD support to the inline asm causes
> the build problem.
>
> I have reproduced problem locally, let me try to debug it.
It seems this patch depends on a65655d40c8235. I have backported it an
am proceeding with testing.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-06-14 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220328091116.GA26815@amd>
[not found] ` <1346806064.1124697.1649068981110@webmail.strato.com>
[not found] ` <20220404112733.GA9863@duo.ucw.cz>
[not found] ` <971433328.1146259.1649072970767@webmail.strato.com>
[not found] ` <86774150.3004766.1651578900027@webmail.strato.com>
[not found] ` <20220503130137.GA12566@duo.ucw.cz>
[not found] ` <1032096920.483689.1652714463015@webmail.strato.com>
[not found] ` <20220517091848.GA29900@duo.ucw.cz>
[not found] ` <1414117524.1401631.1654239722410@webmail.strato.com>
[not found] ` <1772872442.3583605.1654764609414@webmail.strato.com>
2022-06-13 10:30 ` 4.4 backports -- x86 speculation Pavel Machek
[not found] ` <16F8276E2E3F8D91.11238@lists.cip-project.org>
2022-06-14 10:13 ` [cip-dev] " Pavel Machek
[not found] ` <16F8751F2AB1EA42.18003@lists.cip-project.org>
2022-06-14 10:58 ` Pavel Machek
[not found] ` <16F8778C49247DE6.18003@lists.cip-project.org>
2022-06-14 11:10 ` Pavel Machek [this message]
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=20220614111024.GC20387@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=uli@fpond.eu \
/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