[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhTQMo11s7mWg=zzDusJompOp01uJat-q9HjQCoEWzHRRQ@mail.gmail.com>
Date: Fri, 1 Nov 2024 13:11:05 -0400
From: Paul Moore <paul@...l-moore.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, naresh.kamboju@...aro.org, casey@...aufler-ca.com,
anders.roxell@...aro.org, arnd@...db.de, brauner@...nel.org,
dan.carpenter@...aro.org, kees@...nel.org, linux-kernel@...r.kernel.org,
lkft-triage@...ts.linaro.org, ojeda@...nel.org, regressions@...ts.linux.dev,
rust-for-linux@...r.kernel.org, linux-security-module@...r.kernel.org,
lkft@...aro.org
Subject: Re: [PATCH] rust: lsm: replace context+len with lsm_context
On Fri, Nov 1, 2024 at 1:04 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
> On Fri, Nov 1, 2024 at 5:56 PM Paul Moore <paul@...l-moore.com> wrote:
> >
> > Thanks Alice. Would you like me to pull this in via the LSM tree with
> > the associated LSM changes, or would you prefer to do this some other
> > way?
> >
> > I'm going to merge this into lsm/dev for now so that we fix the issue
> > in linux-next, but I'm happy to drop it or do something else, let me
> > know.
>
> Christian has the VFS side, and both are needed for this -- do you
> mean you will cross-merge vfs' branch too?
I think our last emails crossed paths. I'm not going to merge this
via the LSM tree as we don't have the Rust security.c helpers.
Ideally it would have been better to have the Rust LSM/security
helpers in the LSM tree for reasons like this, but it looks like it's
too late for that now.
> By the way, merging both vfs.rust.file and lsm/dev I confirm this builds fine:
>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
Thanks for the build test!
--
paul-moore.com
Powered by blists - more mailing lists