Improved guidance for LSM submissions.
Paul Moore
paul at paul-moore.com
Fri Jan 9 18:51:36 UTC 2026
On Thu, Jan 8, 2026 at 11:08 AM Dr. Greg <greg at enjellic.com> wrote:
>
> What is not clear in these guidelines is how a virgin LSM should be
> structured for initial submission. Moving forward, we believe the
> community would benefit from having clear guidance on this issue.
>
> It would be helpful if the guidance covers a submission of 10-15 KLOC
> of code and 5-8 compilation units, which seems to cover the average
> range of sizes for LSM's that have significant coverage of the event
> handlers/hooks.
I would suggest looking at the existing Linux kernel documentation on
submitting patches, a link is provided below. The entire
document/page is worth reading in full, but the "Separate your
changes" section seems to be most relevant to your question above.
https://docs.kernel.org/process/submitting-patches.html
Beyond that general guidance, at this particular moment I do not have
the cycles to draft a LSM specific recommendation beyond what has
already been documented and reviewed. As usual, the mailing list
archives are also an excellent resource that can be used to
familiarize yourself with community norms and expectations.
--
paul-moore.com
More information about the Linux-security-module-archive
mailing list