From: Ravi Kumar Siddojigari <rsiddoji@codeaurora.org>
To: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
sds@tycho.nsa.gov
Cc: rsiddoji@codeaurora.org, Jaihind Yadav <jaihindyadav@codeaurora.org>
Subject: Re: Looks like issue in handling active_nodes count in 4.19 kernel
Date: Fri, 20 Dec 2019 17:33:01 +0530 [thread overview]
Message-ID: <1576843382-24184-1-git-send-email-rsiddoji@codeaurora.org> (raw)
In-Reply-To: <CAHC9VhSv9BsjqNtwdpAv1yj630L-k8UBcWA5bwC9ySevrPw34w@mail.gmail.com>
Thanks for correcting , Adding the signoff of orginal author in the
following commit .
From 6308b405e2097ab9d82c5a3894815daf7331e0b6 Mon Sep 17 00:00:00 2001
From: Jaihind Yadav <jaihindyadav@codeaurora.org>
Date: Tue, 17 Dec 2019 17:25:47 +0530
Subject: [PATCH] selinux: ensure we cleanup the internal AVC counters on error
in avc_update()
To: rsiddoji@codeaurora.org
In AVC update we don't call avc_node_kill() when avc_xperms_populate()
fails, resulting in the avc->avc_cache.active_nodes counter having a
false value.In last patch this changes was missed , so correcting it.
Signed-off-by: Jaihind Yadav <jaihindyadav@codeaurora.org>
Signed-off-by: Ravi Kumar Siddojigari <rsiddoji@codeaurora.org>
---
security/selinux/avc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/selinux/avc.c b/security/selinux/avc.c
index ecd3829996aa..9c69e83834b0 100644
--- a/security/selinux/avc.c
+++ b/security/selinux/avc.c
@@ -907,7 +907,7 @@ static int avc_update_node(struct selinux_avc *avc,
if (orig->ae.xp_node) {
rc = avc_xperms_populate(node, orig->ae.xp_node);
if (rc) {
- kmem_cache_free(avc_node_cachep, node);
+ avc_node_kill(avc, node);
goto out_unlock;
}
}
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2019-12-20 12:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0101016eeb5fdf43-18f58c0b-8670-43eb-ad08-60dae381f0fd-000000@us-west-2.amazonses.com>
2019-12-09 18:05 ` Looks like issue in handling active_nodes count in 4.19 kernel Stephen Smalley
2019-12-09 18:30 ` rsiddoji
2019-12-11 14:37 ` Stephen Smalley
2019-12-11 14:47 ` Stephen Smalley
2019-12-11 15:35 ` rsiddoji
[not found] ` <0101016ef59a2152-41e65aac-8784-4401-b20d-45b2852872d4-000000@us-west-2.amazonses.com>
2019-12-11 15:53 ` Stephen Smalley
2019-12-17 15:40 ` Ravi Kumar Siddojigari
2019-12-17 15:52 ` Stephen Smalley
2019-12-17 16:23 ` Stephen Smalley
2019-12-18 5:58 ` Ravi Kumar Siddojigari
2019-12-18 13:53 ` Stephen Smalley
2019-12-19 2:20 ` Paul Moore
2019-12-19 9:48 ` Ravi Kumar Siddojigari
2019-12-19 16:00 ` Stephen Smalley
2019-12-19 18:11 ` Paul Moore
2019-12-20 12:03 ` Ravi Kumar Siddojigari [this message]
2019-12-21 16:02 ` 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=1576843382-24184-1-git-send-email-rsiddoji@codeaurora.org \
--to=rsiddoji@codeaurora.org \
--cc=jaihindyadav@codeaurora.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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).