[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1043585: Update on this issue



Hi Salvatore,

Ah, I see what you mean for the links, its an unfortunate copy paste error, I apologize about the duplicated links.

For clarification, it really should have been this one:

https://bugzilla.kernel.org/show_bug.cgi?id=217796

and this:

https://bugzilla.kernel.org/show_bug.cgi?id=217799

Both are issues related to the patch which also is breaking the emulated TPM.

Glad that all this info is helping to get this issue resolved :-)

Kind Regards,

Martin.

On 17/08/2023 19:32, Salvatore Bonaccorso wrote:
Hi Martin,

On Thu, Aug 17, 2023 at 05:10:44PM +0100, Martin Johnson wrote:
Hi Salvadore,

Thanks for getting in contact regarding this issue,

Yes I did mean to reference the two bugzilla entries, since it seems to be
the same patch that's causing issues with the emulated TPM, at least turning
off the mitigation the same way they do fixes the problem for me also with
the swtpm function.
Still confused as the two links were the same, twice
https://bugzilla.kernel.org/show_bug.cgi?id=217796

I did try to apply "x86/retpoline: Don't clobber RFLAGS during
srso_safe_ret()" patch as suggested, unfortunately it is incompatible with
the 6.1.38 Debian kernel source:

--- I omitted some lines as there is a ton of text ---

Applying patch 0052-Linux-6.1.33-rt11-REBASE.patch
Now at patch 0052-Linux-6.1.33-rt11-REBASE.patch
make[2]: Leaving directory
'/home/martin/opt/kernel/debian_test/linux-6.1.38'
make[1]: Leaving directory
'/home/martin/opt/kernel/debian_test/linux-6.1.38'
Importing patch /home/martin/opt/kernel/debian_test/patch.patch (stored as
debian/patches/test/patch.patch)
Applying patch debian/patches/test/patch.patch
patching file arch/x86/lib/retpoline.S
Hunk #1 FAILED at 164.
Hunk #2 FAILED at 239.
Hunk #3 FAILED at 252.
3 out of 3 hunks FAILED -- rejects in file arch/x86/lib/retpoline.S
Patch debian/patches/test/patch.patch does not apply (enforce with -f)
Okay this needs adjustment for 6.1.y.

Thanks for confirming the issue beeing present as well in 6.4.11
upstream and fixed with cherry-picking the commit, this is helpful.

Regards,
Salvatore


Reply to: