From: Paul Moore <paul@paul-moore.com>
To: "Dr. Greg" <greg@enjellic.com>
Cc: linux-security-module@vger.kernel.org
Subject: Re: TSEM code organization.
Date: Sun, 17 Mar 2024 15:20:53 -0400 [thread overview]
Message-ID: <CAHC9VhQC4YvE5LyG76sOsCihBxdrMS8ekLuuOCAAPcLwuwjYdw@mail.gmail.com> (raw)
In-Reply-To: <20240316104714.GA22794@wind.enjellic.com>
On Sat, Mar 16, 2024 at 6:47 AM Dr. Greg <greg@enjellic.com> wrote:
>
> Good morning Paul, I hope your weekend is going well or your week is
> starting well, whenever this e-mail finds you.
>
> We've been waiting for the release of 6.8 for the V3 release of TSEM.
> TSEM seems to be co-habitating with it reasonably well, modulo some
> atomic structure magazine refill issues we are sorting out that appear
> to be caused by workqueue scheduling latency differences between this
> kernel and older kernels, so we are getting ready to push the V3
> release.
>
> Casey has previously raised an issue with the fact that we used a
> single include file, tsem.h, for all of the entities that are global
> to the various compilation units. We placed that file first in the
> patch series so that it could be referenced for review as the
> individual compilation units were added ...
Considering that there are still a number of concerns around the
design of TSEM I wouldn't worry too much about the smaller, easier to
change implementation details, like header file organization at this
point in time. If you've got something that is functional, that
should be sufficient. We still need to sort out if the basic design
and TSEM concepts are acceptable upstream.
--
paul-moore.com
prev parent reply other threads:[~2024-03-17 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 10:47 TSEM code organization Dr. Greg
2024-03-17 19:20 ` Paul Moore [this message]
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=CAHC9VhQC4YvE5LyG76sOsCihBxdrMS8ekLuuOCAAPcLwuwjYdw@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=greg@enjellic.com \
--cc=linux-security-module@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).