From: Yicong Hui <yiconghui@gmail.com>
To: Fan Wu <wufan@kernel.org>
Cc: paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com
Subject: Re: [PATCH] ipe: remove headers that are included but not used
Date: Sat, 6 Dec 2025 21:04:13 +0000 [thread overview]
Message-ID: <3748b276-6503-4c50-a394-e5b75c1eb7bf@gmail.com> (raw)
In-Reply-To: <CAKtyLkEyD9UVxqbmODVOAymE32aE7X4Xdbqj6H3BMGyhn_PQqw@mail.gmail.com>
On 12/3/25 10:25 PM, Fan Wu wrote:
> On Wed, Dec 3, 2025 at 11:37 AM Yicong Hui <yiconghui@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
next prev parent reply other threads:[~2025-12-06 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 19:37 [PATCH] ipe: remove headers that are included but not used Yicong Hui
2025-12-03 22:25 ` Fan Wu
2025-12-06 21:04 ` Yicong Hui [this message]
2025-12-08 19:02 ` Fan Wu
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=3748b276-6503-4c50-a394-e5b75c1eb7bf@gmail.com \
--to=yiconghui@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=wufan@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).