From: Alice Ryhl <aliceryhl@google.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
naresh.kamboju@linaro.org, casey@schaufler-ca.com,
anders.roxell@linaro.org, arnd@arndb.de, brauner@kernel.org,
dan.carpenter@linaro.org, kees@kernel.org,
linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
ojeda@kernel.org, regressions@lists.linux.dev,
rust-for-linux@vger.kernel.org,
linux-security-module@vger.kernel.org, lkft@linaro.org
Subject: Re: [PATCH] rust: lsm: replace context+len with lsm_context
Date: Fri, 1 Nov 2024 18:23:47 +0100 [thread overview]
Message-ID: <CAH5fLgi+JJHCA_XTPC0-kaacZC6=aGSa-+DiNt06GSJNFhKc3w@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhTQMo11s7mWg=zzDusJompOp01uJat-q9HjQCoEWzHRRQ@mail.gmail.com>
On Fri, Nov 1, 2024 at 6:11 PM Paul Moore <paul@paul-moore.com> wrote:
>
> On Fri, Nov 1, 2024 at 1:04 PM Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
> > On Fri, Nov 1, 2024 at 5:56 PM Paul Moore <paul@paul-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.
If Christian is okay with rewriting the vfs.rust.file tree, we can
drop commit 94d356c0335f ("rust: security: add abstraction for
secctx") from there and I'll update it and send it for inclusion in
the LSM tree instead. I'll need to drop the piece that ties together
`struct cred` and `secctx` from the patch, but I can follow up with a
small patch for that for the 6.14 merge window.
Alice
next prev parent reply other threads:[~2024-11-01 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 9:01 next-20241101: rust/kernel/security.rs - error[E0061]: this function takes 2 arguments but 3 arguments were supplied Naresh Kamboju
2024-11-01 9:56 ` [PATCH] rust: lsm: replace context+len with lsm_context Alice Ryhl
2024-11-01 16:56 ` Paul Moore
2024-11-01 17:02 ` Paul Moore
2024-11-27 4:17 ` Paul Moore
2024-11-01 17:03 ` Miguel Ojeda
2024-11-01 17:11 ` Paul Moore
2024-11-01 17:23 ` Alice Ryhl [this message]
2024-11-01 17:48 ` [PATCH] rust: security: add abstraction for secctx Alice Ryhl
2024-11-01 17:59 ` [PATCH] rust: lsm: replace context+len with lsm_context Paul Moore
2024-11-01 18:08 ` Alice Ryhl
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='CAH5fLgi+JJHCA_XTPC0-kaacZC6=aGSa-+DiNt06GSJNFhKc3w@mail.gmail.com' \
--to=aliceryhl@google.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dan.carpenter@linaro.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=naresh.kamboju@linaro.org \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=regressions@lists.linux.dev \
--cc=rust-for-linux@vger.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).