From: Mark Brown <broonie@kernel.org>
To: Paul Moore <paul@paul-moore.com>
Cc: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Stanislav Kinsburskii" <skinsburskii@gmail.com>
Subject: linux-next: manual merge of the audit tree with the origin tree
Date: Fri, 16 Oct 2026 13:28:36 +0100 [thread overview]
Message-ID: <atIYdNSykms3dLCk@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
Hi all,
Today's linux-next merge of the audit tree got a conflict in:
kernel/audit_tree.c
between commit:
aa650d87a4988 ("audit: fix exe mark UAF in kill_rules()")
from the origin tree and commit:
ca12826b4aac8 ("audit: Fix filter rule accounting after automatic removal")
from the audit tree. I'm really unsure about this merge, it's not clear
to me if the unaccounting should go in the initial loop or the RCU free
loop.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc kernel/audit_tree.c
index f2e81be8265e8,2d68d2ec2b2a1..0000000000000
--- a/kernel/audit_tree.c
+++ b/kernel/audit_tree.c
@@@ -573,9 -550,17 +573,10 @@@ static void kill_rules(struct audit_con
entry = container_of(rule, struct audit_entry, rule);
list_del_init(&rule->rlist);
- if (rule->tree) {
- /* not a half-baked one */
- audit_tree_log_remove_rule(context, rule);
- if (entry->rule.exe)
- audit_remove_mark(entry->rule.exe);
- rule->tree = NULL;
- list_del_rcu(&entry->list);
- list_del(&entry->rule.list);
- audit_rule_unaccount(rule);
- call_rcu(&entry->rcu, audit_free_rule_rcu);
- }
+ if (entry->rule.exe)
+ audit_remove_mark(entry->rule.exe);
++ audit_rule_unaccount(rule);
+ call_rcu(&entry->rcu, audit_free_rule_rcu);
}
}
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-10-16 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 12:28 Mark Brown [this message]
2026-10-16 13:49 ` linux-next: manual merge of the audit tree with the origin tree 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=atIYdNSykms3dLCk@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=skinsburskii@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox