From: Tushar Sugandhi <tusharsu@linux.microsoft.com> To: Stefan Berger <stefanb@linux.ibm.com>, zohar@linux.ibm.com, roberto.sassu@huaweicloud.com, roberto.sassu@huawei.com, eric.snowberg@oracle.com, ebiederm@xmission.com, noodles@fb.com, bauermann@kolabnow.com, linux-integrity@vger.kernel.org, kexec@lists.infradead.org Cc: code@tyhicks.com, nramas@linux.microsoft.com, paul@paul-moore.com Subject: Re: [PATCH v5 4/8] ima: kexec: define functions to copy IMA log at soft boot Date: Wed, 14 Feb 2024 22:55:54 -0800 [thread overview] Message-ID: <6c7158ef-2b12-4ba4-afc5-7618357d3aa4@linux.microsoft.com> (raw) In-Reply-To: <4189d465-dafc-4cf8-80d2-972f60bb6214@linux.ibm.com> On 2/14/24 12:47, Stefan Berger wrote: > > > On 2/14/24 10:38, Tushar Sugandhi wrote: ... <snip/> ... >> +void kimage_file_post_load(struct kimage *image) >> +{ >> + ima_kexec_post_load(image); >> +} >> + > > We get this here at this point but it disappears later -- missing header? > > kernel/kexec_file.c:189:6: warning: no previous prototype for > ‘kimage_file_post_load’ [-Wmissing-prototypes] > 189 | void kimage_file_post_load(struct kimage *image) > | ^~~~~~~~~~~~~~~~~~~~~ > > Thanks Stefan. I was also getting it. But couldn't figure out why. And I was puzzled why it was going away. Since kimage_file_post_load() is called from the same file in patch 5/8, I don't see a need of declaring it in a header file like include/linux/kexec.h. Making kimage_file_post_load() local static resolves the warning. But then it throws "defined but not used" warning. I will have to call it from kexec_file_load syscall in this patch (4/8) instead 5/8 to resolve that warning. I will make the function a stub function in this patch and make it call ima_kexec_post_load(image) in the next patch to avoid any potential bisect safe issues. It aligns with the goals of patch 4/8 and 5/8 anyways. +static void kimage_file_post_load(struct kimage *image) +{ + /* + * this will call ima_kexec_post_load(image) to map the segment + * and register the reboot notifier for moving the IMA log at + * kexec execute + */ +} + @@ -410,6 +410,9 @@ SYSCALL_DEFINE5(kexec_file_load, int, kernel_fd, int, initrd_fd, kimage_terminate(image); + if (!(flags & KEXEC_FILE_ON_CRASH)) + kimage_file_post_load(image); + ... ...<snip/> ... > > Reviewed-by: Stefan Berger <stefanb@linux.ibm.com> Thanks for the tag. I will apply it on the next version. ~Tushar _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Tushar Sugandhi <tusharsu@linux.microsoft.com> To: Stefan Berger <stefanb@linux.ibm.com>, zohar@linux.ibm.com, roberto.sassu@huaweicloud.com, roberto.sassu@huawei.com, eric.snowberg@oracle.com, ebiederm@xmission.com, noodles@fb.com, bauermann@kolabnow.com, linux-integrity@vger.kernel.org, kexec@lists.infradead.org Cc: code@tyhicks.com, nramas@linux.microsoft.com, paul@paul-moore.com Subject: Re: [PATCH v5 4/8] ima: kexec: define functions to copy IMA log at soft boot Date: Wed, 14 Feb 2024 22:55:54 -0800 [thread overview] Message-ID: <6c7158ef-2b12-4ba4-afc5-7618357d3aa4@linux.microsoft.com> (raw) In-Reply-To: <4189d465-dafc-4cf8-80d2-972f60bb6214@linux.ibm.com> On 2/14/24 12:47, Stefan Berger wrote: > > > On 2/14/24 10:38, Tushar Sugandhi wrote: ... <snip/> ... >> +void kimage_file_post_load(struct kimage *image) >> +{ >> + ima_kexec_post_load(image); >> +} >> + > > We get this here at this point but it disappears later -- missing header? > > kernel/kexec_file.c:189:6: warning: no previous prototype for > ‘kimage_file_post_load’ [-Wmissing-prototypes] > 189 | void kimage_file_post_load(struct kimage *image) > | ^~~~~~~~~~~~~~~~~~~~~ > > Thanks Stefan. I was also getting it. But couldn't figure out why. And I was puzzled why it was going away. Since kimage_file_post_load() is called from the same file in patch 5/8, I don't see a need of declaring it in a header file like include/linux/kexec.h. Making kimage_file_post_load() local static resolves the warning. But then it throws "defined but not used" warning. I will have to call it from kexec_file_load syscall in this patch (4/8) instead 5/8 to resolve that warning. I will make the function a stub function in this patch and make it call ima_kexec_post_load(image) in the next patch to avoid any potential bisect safe issues. It aligns with the goals of patch 4/8 and 5/8 anyways. +static void kimage_file_post_load(struct kimage *image) +{ + /* + * this will call ima_kexec_post_load(image) to map the segment + * and register the reboot notifier for moving the IMA log at + * kexec execute + */ +} + @@ -410,6 +410,9 @@ SYSCALL_DEFINE5(kexec_file_load, int, kernel_fd, int, initrd_fd, kimage_terminate(image); + if (!(flags & KEXEC_FILE_ON_CRASH)) + kimage_file_post_load(image); + ... ...<snip/> ... > > Reviewed-by: Stefan Berger <stefanb@linux.ibm.com> Thanks for the tag. I will apply it on the next version. ~Tushar
next prev parent reply other threads:[~2024-02-15 6:56 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-14 15:38 [PATCH v5 0/8] ima: kexec: measure events between kexec load and execute Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-14 15:38 ` [PATCH v5 1/8] ima: define and call ima_alloc_kexec_file_buf Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-19 22:16 ` Stefan Berger 2024-02-19 22:16 ` Stefan Berger 2024-02-21 0:12 ` Mimi Zohar 2024-02-21 0:12 ` Mimi Zohar 2024-02-14 15:38 ` [PATCH v5 2/8] kexec: define functions to map and unmap segments Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-14 19:43 ` Stefan Berger 2024-02-14 19:43 ` Stefan Berger 2024-02-15 6:13 ` Tushar Sugandhi 2024-02-15 6:13 ` Tushar Sugandhi 2024-02-21 20:22 ` Mimi Zohar 2024-02-21 20:22 ` Mimi Zohar 2024-02-14 15:38 ` [PATCH v5 3/8] ima: kexec: skip IMA segment validation after kexec soft reboot Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-14 15:38 ` [PATCH v5 4/8] ima: kexec: define functions to copy IMA log at soft boot Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-14 20:47 ` Stefan Berger 2024-02-14 20:47 ` Stefan Berger 2024-02-15 6:55 ` Tushar Sugandhi [this message] 2024-02-15 6:55 ` Tushar Sugandhi 2024-02-21 21:52 ` Mimi Zohar 2024-02-21 21:52 ` Mimi Zohar 2024-02-21 22:39 ` Mimi Zohar 2024-02-21 22:39 ` Mimi Zohar 2024-03-01 11:12 ` Petr Tesařík 2024-03-01 11:12 ` Petr Tesařík 2024-02-14 15:38 ` [PATCH v5 5/8] ima: kexec: move IMA log copy from kexec load to execute Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-14 20:58 ` Stefan Berger 2024-02-14 20:58 ` Stefan Berger 2024-02-22 1:47 ` Mimi Zohar 2024-02-22 1:47 ` Mimi Zohar 2024-05-09 6:32 ` Petr Tesařík 2024-05-09 6:32 ` Petr Tesařík 2024-02-14 15:38 ` [PATCH v5 6/8] ima: suspend measurements during buffer copy at kexec execute Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-22 14:14 ` Mimi Zohar 2024-02-22 14:14 ` Mimi Zohar 2024-02-22 16:38 ` Mimi Zohar 2024-02-22 16:38 ` Mimi Zohar 2024-02-29 13:21 ` Petr Tesařík 2024-02-29 13:21 ` Petr Tesařík 2024-02-14 15:38 ` [PATCH v5 7/8] ima: make the kexec extra memory configurable Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-22 14:13 ` Mimi Zohar 2024-02-22 14:13 ` Mimi Zohar 2024-02-14 15:38 ` [PATCH v5 8/8] ima: measure kexec load and exec events as critical data Tushar Sugandhi 2024-02-14 15:38 ` Tushar Sugandhi 2024-02-14 21:00 ` Stefan Berger 2024-02-14 21:00 ` Stefan Berger 2024-02-15 6:57 ` Tushar Sugandhi 2024-02-15 6:57 ` Tushar Sugandhi 2024-02-14 21:03 ` Stefan Berger 2024-02-14 21:03 ` Stefan Berger 2024-02-15 6:58 ` Tushar Sugandhi 2024-02-15 6:58 ` Tushar Sugandhi 2024-02-21 0:15 ` [PATCH v5 0/8] ima: kexec: measure events between kexec load and execute Mimi Zohar 2024-02-21 0:15 ` Mimi Zohar
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=6c7158ef-2b12-4ba4-afc5-7618357d3aa4@linux.microsoft.com \ --to=tusharsu@linux.microsoft.com \ --cc=bauermann@kolabnow.com \ --cc=code@tyhicks.com \ --cc=ebiederm@xmission.com \ --cc=eric.snowberg@oracle.com \ --cc=kexec@lists.infradead.org \ --cc=linux-integrity@vger.kernel.org \ --cc=noodles@fb.com \ --cc=nramas@linux.microsoft.com \ --cc=paul@paul-moore.com \ --cc=roberto.sassu@huawei.com \ --cc=roberto.sassu@huaweicloud.com \ --cc=stefanb@linux.ibm.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.