Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tushar Sugandhi <tusharsu@linux.microsoft.com>
To: Jonathan McDowell <noodles@fb.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Alasdair G Kergon <agk@redhat.com>,
	Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
	Tyler Hicks <tyhicks@linux.microsoft.com>
Subject: Re: need help: patches to capture events between kexec load and execute
Date: Mon, 6 Jun 2022 10:22:39 -0700	[thread overview]
Message-ID: <7452c305-dad4-2836-1d21-1c051f15f11c@linux.microsoft.com> (raw)
In-Reply-To: <Yp24dc/i8XU9A+5/@noodles-fedora.dhcp.thefacebook.com>

Hi Jonathan,
Thank you for taking a look at my patches.

On 6/6/22 01:19, Jonathan McDowell wrote:
> The main piece that seems to be missing is updating the size of the IMA
> buffer in the mechanism used to pass its details to the new kernel (so
> device tree in current mainline [setup_ima_buffer], the setup_data piece
> in my x86_64 patches). Without that you'll only load the original set of
> measurements even if the extra data is in the buffer.

Ok. Thanks for the pointer.
I will take a look at your patches and get back to you with updates.
> 
> I think there's also a potential problem in that you assume an extra
> page is sufficient for any additional measurements which may or may not
> be the case - I don't see any check in ima_update_kexec_buffer that the
> buffer is big enough for the new IMA data.
> 
Agreed.  I wanted to solve that problem next.
First I wanted to verify at least a few events are getting copied after
the kexec soft reboot.
But thanks for pointing this out.
> J.

Again, appreciate your pointers.

Thanks,
Tushar

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2022-06-06 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04  6:16 need help: patches to capture events between kexec load and execute Tushar Sugandhi
2022-06-06  8:19 ` Jonathan McDowell
2022-06-06 17:22   ` Tushar Sugandhi [this message]
     [not found]   ` <87775c1e-d1d3-519c-599b-30cdb1691cb2@linux.microsoft.com>
2023-05-31 11:39     ` Mimi Zohar
     [not found]       ` <41270374-dc5e-3aa2-d2ed-9b8fc73ad65f@linux.microsoft.com>
2023-05-31 22:43         ` Mimi Zohar
2023-06-06 15:37           ` Stefan Berger
2023-06-06 15:59             ` Mimi Zohar
2023-06-07 18:42               ` Stefan Berger

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=7452c305-dad4-2836-1d21-1c051f15f11c@linux.microsoft.com \
    --to=tusharsu@linux.microsoft.com \
    --cc=agk@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=noodles@fb.com \
    --cc=nramas@linux.microsoft.com \
    --cc=tyhicks@linux.microsoft.com \
    --cc=zohar@linux.ibm.com \
    /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