On 22/01/2025 05:36, Dave Young wrote:
> Hi,
> On Mon, 20 Jan 2025 at 19:48, Usama Arif wrote:
>>
>>
>>
>> On 20/01/2025 11:29, Ard Biesheuvel wrote:
>>> On Mon, 20 Jan 2025 at 11:50, Usama Arif wrote:
>>>>
>>>>
>>>>
&
On 20/01/2025 11:29, Ard Biesheuvel wrote:
> On Mon, 20 Jan 2025 at 11:50, Usama Arif wrote:
>>
>>
>>
>> On 20/01/2025 10:32, Ard Biesheuvel wrote:
>>> On Mon, 20 Jan 2025 at 11:27, Usama Arif wrote:
>>>>
>>>>
>>> ...
>
On 20/01/2025 10:32, Ard Biesheuvel wrote:
> On Mon, 20 Jan 2025 at 11:27, Usama Arif wrote:
>>
>>
> ...
>> Hi Ard,
>>
>> Just wanted to check how should we proceed forward? Should we try and fix
>> the warning
>> and corruption during kexec
On 13/01/2025 12:00, Usama Arif wrote:
>
>
> On 13/01/2025 11:27, Usama Arif wrote:
>>
>>
>> On 13/01/2025 02:33, Dave Young wrote:
>>> On Fri, 10 Jan 2025 at 18:54, Usama Arif wrote:
>>>>
>>>>
>>>>
>>>> On 1
On 13/01/2025 02:33, Dave Young wrote:
> On Fri, 10 Jan 2025 at 18:54, Usama Arif wrote:
>>
>>
>>
>> On 10/01/2025 07:21, Ard Biesheuvel wrote:
>>> On Thu, 9 Jan 2025 at 17:36, Usama Arif wrote:
>>>>
>>>>
>>>>
>>&
On 13/01/2025 11:27, Usama Arif wrote:
>
>
> On 13/01/2025 02:33, Dave Young wrote:
>> On Fri, 10 Jan 2025 at 18:54, Usama Arif wrote:
>>>
>>>
>>>
>>> On 10/01/2025 07:21, Ard Biesheuvel wrote:
>>>> On Thu, 9 Jan 2025 at 17:36,
On 10/01/2025 07:21, Ard Biesheuvel wrote:
> On Thu, 9 Jan 2025 at 17:36, Usama Arif wrote:
>>
>>
>>
>> On 09/01/2025 15:45, Ard Biesheuvel wrote:
>>> On Wed, 8 Jan 2025 at 23:00, Usama Arif wrote:
>>>>
>>>> The commit in [1] intro
On 10/01/2025 11:20, Dave Young wrote:
> On Fri, 10 Jan 2025 at 19:18, Dave Young wrote:
>>
>> On Fri, 10 Jan 2025 at 19:12, Usama Arif wrote:
>>>
>>>
>>>
>>> On 10/01/2025 02:50, Dave Young wrote:
>>>> Hi Usama,
>>>>
On 10/01/2025 14:31, Usama Arif wrote:
>
>
> On 10/01/2025 07:32, Ard Biesheuvel wrote:
>> On Thu, 9 Jan 2025 at 17:32, Usama Arif wrote:
>>>
>>>
>>>
>>> On 09/01/2025 16:15, Ard Biesheuvel wrote:
>
>>> I think in the end whoeve
On 10/01/2025 07:32, Ard Biesheuvel wrote:
> On Thu, 9 Jan 2025 at 17:32, Usama Arif wrote:
>>
>>
>>
>> On 09/01/2025 16:15, Ard Biesheuvel wrote:
>> I think in the end whoevers' responsibility it is, the easiest path forward
>> seems t
On 09/01/2025 15:45, Ard Biesheuvel wrote:
> On Wed, 8 Jan 2025 at 23:00, Usama Arif wrote:
>>
>> The commit in [1] introduced a check to see if EFI memory attributes
>> table was corrupted. It assumed that efi.memmap.nr_map remains
>> constant, but it changes duri
On 09/01/2025 16:15, Ard Biesheuvel wrote:
> On Wed, 8 Jan 2025 at 23:00, Usama Arif wrote:
>>
>> When this area is not reserved, it comes up as usable in
>> /sys/firmware/memmap. This means that kexec, which uses that memmap
>> to find usable memory regions,
On 10/01/2025 02:50, Dave Young wrote:
> Hi Usama,
>
> On Thu, 9 Jan 2025 at 06:00, Usama Arif wrote:
>>
>> When this area is not reserved, it comes up as usable in
>> /sys/firmware/memmap. This means that kexec, which uses that memmap
>> to find usable memo
Hi,
We (meta) are seeing the below warning in production machines for all kernels
from 5.12 to 6.11 during boot which results in tpm probe failing:
[6.388599] [ cut here ]
On 11/09/2024 12:51, Ard Biesheuvel wrote:
> On Wed, 11 Sept 2024 at 12:41, Usama Arif wrote:
>>
>> Looking at the TPM spec [1]
>>
>> If the ACPI TPM2 table contains the address and size of the Platform
>> Firmware TCG log, firmware “pins” the memory associated
On 11/09/2024 12:51, Ard Biesheuvel wrote:
> On Wed, 11 Sept 2024 at 12:41, Usama Arif wrote:
>>
>> Looking at the TPM spec [1]
>>
>> If the ACPI TPM2 table contains the address and size of the Platform
>> Firmware TCG log, firmware “pins” the memory associated
On 10/09/2024 15:26, Eric W. Biederman wrote:
> Breno Leitao writes:
>
>> We've seen a problem in upstream kernel kexec, where a EFI TPM log event
>> table
>> is being overwritten. This problem happen on real machine, as well as in a
>> recent EDK2 qemu VM.
>>
>> Digging deep, the table is b
e820_table_firmware. I believe the proper
fix should be in efi firmware, which might be a bit difficult to get through.
But with the below secondary fix in kernel, the corruption is gone, it would be
good to have efi, tpm and kexec experts to look at this and tell if it makes
sense?
Than
18 matches
Mail list logo
