[PATCH] ipe: remove headers that are included but not used
Yicong Hui
yiconghui at gmail.com
Sat Dec 6 21:04:13 UTC 2025
On 12/3/25 10:25 PM, Fan Wu wrote:
> On Wed, Dec 3, 2025 at 11:37 AM Yicong Hui <yiconghui at gmail.com> wrote:
>
> Hi Yicong,
>
> Thanks for the patch. This kind of cleanup is appreciated.
>
> Commit message typo: "audit. c, audit.c, policy. c" - audit. c is listed
> twice.
Hi! Thank you for the reply! Yes! My bad, this typo will be fixed in v2.
> I was trying to verify whether ipe.h is really not needed and found
> that these files are missing explicit dependencies. policy.c and
> policy_fs.c use rcu, mutex, and slab functions but rely on transitive
> includes. After removing ipe.h, they still compile because eval.h
> also happens to provide these dependencies indirectly.
>
> I'm happy to merge a patch removing unused headers like ipe.h, but
> would like to see the implicit dependencies resolved as well. Would
> you mind tracing the complete dependencies and adding the explicit
> includes in v2?
I have manually read through the functions/macros/filetypes in policy.c,
policy_fs.c and audit.c and found a few dependencies that are used but
not explicitly included, like minmax.h, sha2.h, lockdep.h, string.h,
capability.h, kstrtox.h, sprintf.h, array_size.h and err.h.
This might be a stupid question, but how explicit should I be in my v2
patch with the dependencies? There's headers like
"asm-generic/int-ll64.h" "uidgid.h", "gfp_types.h", "rwonce.h",
"compiler_types.h" or "errno-base.h" but I'm not sure to what extent I
need to import them, because I shouldn't be including them all, right?
Thank you!
- Yicong
More information about the Linux-security-module-archive
mailing list