From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
casey@schaufler-ca.com, eparis@redhat.com,
linux-security-module@vger.kernel.org, audit@vger.kernel.org
Cc: jmorris@namei.org, serge@hallyn.com, keescook@chromium.org,
john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp,
stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: [PATCH v6 1/4] Audit: Create audit_stamp structure
Date: Sat, 30 Aug 2025 10:14:37 -0400 [thread overview]
Message-ID: <e6e9ea4bacac5553810f7963533a71ca@paul-moore.com> (raw)
In-Reply-To: <20250816172859.6437-2-casey@schaufler-ca.com>
On Aug 16, 2025 Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> Replace the timestamp and serial number pair used in audit records
> with a structure containing the two elements.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> ---
> kernel/audit.c | 17 +++++++++--------
> kernel/audit.h | 13 +++++++++----
> kernel/auditsc.c | 22 +++++++++-------------
> 3 files changed, 27 insertions(+), 25 deletions(-)
Merged into audit/dev, thanks.
--
paul-moore.com
next prev parent reply other threads:[~2025-08-30 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250816172859.6437-1-casey.ref@schaufler-ca.com>
2025-08-16 17:28 ` [PATCH v6 0/4] Audit: Records for multiple security contexts Casey Schaufler
2025-08-16 17:28 ` [PATCH v6 1/4] Audit: Create audit_stamp structure Casey Schaufler
2025-08-30 14:14 ` Paul Moore [this message]
2025-08-30 15:42 ` Casey Schaufler
2025-08-16 17:28 ` [PATCH v6 2/4] LSM: security_lsmblob_to_secctx module selection Casey Schaufler
2025-08-30 14:14 ` Paul Moore
2025-08-16 17:28 ` [PATCH v6 3/4] Audit: Add record for multiple task security contexts Casey Schaufler
2025-08-30 14:15 ` Paul Moore
2025-08-16 17:28 ` [PATCH v6 4/4] Audit: Add record for multiple object contexts Casey Schaufler
2025-08-30 14:15 ` Paul Moore
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=e6e9ea4bacac5553810f7963533a71ca@paul-moore.com \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.