Re: [PATCH] efi: expose TPM event log to userspace via sysfs
On Fri Apr 26, 2024 at 11:19 AM EEST, Mikko Rapeli wrote: > Hi, > > On Fri, Apr 26, 2024 at 10:40:20AM +0300, Jarkko Sakkinen wrote: > > On Fri Apr 26, 2024 at 10:35 AM EEST, Jarkko Sakkinen wrote: > > > On Thu Apr 25, 2024 at 5:01 PM EEST, Jarkko Sakkinen wrote: > > > > On Thu Apr 25, 2024 at 12:58 PM EEST, Lennart Poettering wrote: > > > > > General purpose distros typically don't build all TPM drivers into the > > > > > kernel, but ship some in the initrd instead. Then, udev is responsible > > > > > for iterating all buses/devices and auto-loading the necessary > > > > > drivers. Each loaded bus driver might make more devices available for > > > > > > > > I've had since day 0 that I've worked with TPM driver (i.e. since 2013 > > > > > > - had the opinion (typo) > > > > Tbh, I have zero idea what this discussion is about anyway because the > > original thread *was not* CC'd to linux-integrity and I'm not subscribed > > to linux-efi. So next time put all the relevant mailing lists. I.e. > > definitive NAK for this patch. > > Sorry for not including linux-integrity. I added maintainers and lists > proposed by scripts/get_maintainers.pl for the change which did not touch > drivers/char/tpm/ though TPM event log APIs are clearly there. > > The full thread starts from here: > > https://lore.kernel.org/all/20240422112711.362779-1-mikko.rap...@linaro.org/T/#u NP, just add CC to the next version. I'll download it and check through once bandwidth. > Cheers, > > -Mikko BR, Jarkko
Re: [PATCH] efi: expose TPM event log to userspace via sysfs
Hi, On Fri, Apr 26, 2024 at 10:40:20AM +0300, Jarkko Sakkinen wrote: > On Fri Apr 26, 2024 at 10:35 AM EEST, Jarkko Sakkinen wrote: > > On Thu Apr 25, 2024 at 5:01 PM EEST, Jarkko Sakkinen wrote: > > > On Thu Apr 25, 2024 at 12:58 PM EEST, Lennart Poettering wrote: > > > > General purpose distros typically don't build all TPM drivers into the > > > > kernel, but ship some in the initrd instead. Then, udev is responsible > > > > for iterating all buses/devices and auto-loading the necessary > > > > drivers. Each loaded bus driver might make more devices available for > > > > > > I've had since day 0 that I've worked with TPM driver (i.e. since 2013 > > > > - had the opinion (typo) > > Tbh, I have zero idea what this discussion is about anyway because the > original thread *was not* CC'd to linux-integrity and I'm not subscribed > to linux-efi. So next time put all the relevant mailing lists. I.e. > definitive NAK for this patch. Sorry for not including linux-integrity. I added maintainers and lists proposed by scripts/get_maintainers.pl for the change which did not touch drivers/char/tpm/ though TPM event log APIs are clearly there. The full thread starts from here: https://lore.kernel.org/all/20240422112711.362779-1-mikko.rap...@linaro.org/T/#u Cheers, -Mikko
Re: [PATCH] efi: expose TPM event log to userspace via sysfs
On Fri Apr 26, 2024 at 10:35 AM EEST, Jarkko Sakkinen wrote: > On Thu Apr 25, 2024 at 5:01 PM EEST, Jarkko Sakkinen wrote: > > On Thu Apr 25, 2024 at 12:58 PM EEST, Lennart Poettering wrote: > > > General purpose distros typically don't build all TPM drivers into the > > > kernel, but ship some in the initrd instead. Then, udev is responsible > > > for iterating all buses/devices and auto-loading the necessary > > > drivers. Each loaded bus driver might make more devices available for > > > > I've had since day 0 that I've worked with TPM driver (i.e. since 2013 > > - had the opinion (typo) Tbh, I have zero idea what this discussion is about anyway because the original thread *was not* CC'd to linux-integrity and I'm not subscribed to linux-efi. So next time put all the relevant mailing lists. I.e. definitive NAK for this patch. BR, Jarkko
Re: [PATCH] efi: expose TPM event log to userspace via sysfs
On Thu Apr 25, 2024 at 5:01 PM EEST, Jarkko Sakkinen wrote: > On Thu Apr 25, 2024 at 12:58 PM EEST, Lennart Poettering wrote: > > General purpose distros typically don't build all TPM drivers into the > > kernel, but ship some in the initrd instead. Then, udev is responsible > > for iterating all buses/devices and auto-loading the necessary > > drivers. Each loaded bus driver might make more devices available for > > I've had since day 0 that I've worked with TPM driver (i.e. since 2013 - had the opinion (typo) BR, Jarkko
