From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <pmoore@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5] audit: save signal match info in case entry passed in is the one deleted
Date: Wed, 5 Aug 2015 15:21:43 -0400 [thread overview]
Message-ID: <20150805192143.GJ32407@madcap2.tricolour.ca> (raw)
In-Reply-To: <1583724.gJuObs13E5@sifl>
On 15/08/05, Paul Moore wrote:
> On Wednesday, August 05, 2015 05:23:10 AM Richard Guy Briggs wrote:
> > Move the access to the entry for audit_match_signal() to the beginning of
> > the function in case the entry found is the same one passed in. This will
> > enable it to be used by audit_remove_mark_rule().
> >
> > Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
> >
> > Revision history:
> > v4 -> v5:
> > Move mutex_unlock after out label.
> > Move list_del group after test for signal to remove temp variable.
> >
> > ---
> > This patch was split out from the audit by executable path patch set due to
> > the potential to use it elsewhere.
> >
> > In particular, some questions came up while assessing the potential for code
> > reuse:
> >
> > Why does audit_remove_parent_watches() not call audit_del_rule() for
> > each entry found?
> > Is audit_signals not properly decremented?
> > Is audit_n_rules not properly decremented?
> >
> > Why does kill_rules() not call audit_del_rule() for each entry
> > found? Is audit_signals not properly decremented?
> > Is audit_n_rules not properly decremented?
> >
> > kernel/auditfilter.c | 13 ++++++++-----
> > 1 files changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/kernel/auditfilter.c b/kernel/auditfilter.c
> > index 4cb9b44..1b110fb 100644
> > --- a/kernel/auditfilter.c
> > +++ b/kernel/auditfilter.c
> > @@ -953,7 +953,6 @@ static inline int audit_del_rule(struct audit_entry
> > *entry) mutex_lock(&audit_filter_mutex);
> > e = audit_find_rule(entry, &list);
> > if (!e) {
> > - mutex_unlock(&audit_filter_mutex);
> > ret = -ENOENT;
> > goto out;
> > }
> > @@ -964,9 +963,8 @@ static inline int audit_del_rule(struct audit_entry
> > *entry) if (e->rule.tree)
> > audit_remove_tree_rule(&e->rule);
> >
> > - list_del_rcu(&e->list);
> > - list_del(&e->rule.list);
> > - call_rcu(&e->rcu, audit_free_rule_rcu);
> > + if (e->rule.exe)
> > + audit_remove_mark_rule(&e->rule);
>
> What?
Wow, whoops! I had to stare at it a while to see what was wrong...
Those last two lines belong in a different patch set...
> I think you munged a cut n' paste somehow. This code doesn't even compile.
That was a local git tree rebase merge conflict manual fix error...
Not a bisect, but with the other patch set, it does. :)
Re-generating audit-by-executable patchset too...
> > #ifdef CONFIG_AUDITSYSCALL
> > if (!dont_count)
> > @@ -975,9 +973,14 @@ static inline int audit_del_rule(struct audit_entry
> > *entry) if (!audit_match_signal(entry))
> > audit_signals--;
> > #endif
> > - mutex_unlock(&audit_filter_mutex);
> > +
> > + list_del_rcu(&e->list);
> > + list_del(&e->rule.list);
> > + call_rcu(&e->rcu, audit_free_rule_rcu);
> >
> > out:
> > + mutex_unlock(&audit_filter_mutex);
> > +
> > if (tree)
> > audit_put_tree(tree); /* that's the temporary one */
>
> paul moore
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
prev parent reply other threads:[~2015-08-05 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 9:23 [PATCH V5] audit: save signal match info in case entry passed in is the one deleted Richard Guy Briggs
2015-08-05 15:12 ` Paul Moore
2015-08-05 19:21 ` Richard Guy Briggs [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=20150805192143.GJ32407@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoore@redhat.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