LSM: Replace secctx/len pairs with lsm_context

Casey Schaufler casey at schaufler-ca.com
Wed Dec 4 17:16:38 UTC 2024


On 12/3/2024 3:06 PM, Paul Moore wrote:
> On Tue, Dec 3, 2024 at 5:54 PM Casey Schaufler <casey at schaufler-ca.com> wrote:
>> On 12/3/2024 1:59 PM, Paul Moore wrote:
>>> On Tue, Dec 3, 2024 at 2:29 PM Casey Schaufler <casey at schaufler-ca.com> wrote:
>>>> Paul, do you want a revised patch set for the lsm_context change,
>>>> or do you want to stick with what's in dev-staging?
>>> I figured I would just move dev-staging over (I've already ported them
>>> to v6.13-rc1 in my tree), but if you want to send out another patchset
>>> I guess that's fine too.  Although looking at the related patches in
>>> dev-staging right now, excluding the rust update from Alice, there is
>>> only a kdoc fix (me), a signedness fix (Dan Carpenter), and then the
>>> two fixes from you.  If you like, I can just squash your fixes into
>>> the relevant patches since there is no authorship issue, and to be
>>> frank I'm fine with squashing my kdoc fix too, which leaves us with
>>> just Dan's fix ... which I think is okay~ish to leave standalone, but
>>> if Dan's okay with squashing that I can do that too as it would be
>>> preferable.  Dan?
>>>
>>> In case anyone is wondering, yes, squashing does take a little bit of
>>> work on my end, but it borders on trivial, and it is much quicker than
>>> re-reviewing a patchset.
>> I figured that it could go either way. I won't resend. Thank you.
> No problem.  Just to be clear, do I have your okay to squash your patches?

Yes. I may have introduced some formatting (e.g. tabs in struct definitions)
that you dislike. Feel free to "correct" any you find as well.




More information about the Linux-security-module-archive mailing list