From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <pmoore@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
sgrubb@redhat.com, eparis@redhat.com, peter@hda3.com
Subject: Re: [PATCH V10] fixup: audit: implement audit by executable
Date: Wed, 12 Aug 2015 05:48:48 -0400 [thread overview]
Message-ID: <20150812094848.GA25337@madcap2.tricolour.ca> (raw)
In-Reply-To: <20150811041504.GC15959@madcap2.tricolour.ca>
On 15/08/11, Richard Guy Briggs wrote:
> On 15/08/10, Paul Moore wrote:
> > On Monday, August 10, 2015 01:29:43 PM Richard Guy Briggs wrote:
> > > On 15/08/10, Paul Moore wrote:
> > > > On Saturday, August 08, 2015 10:20:25 AM Richard Guy Briggs wrote:
> > > > > diff --git a/kernel/audit_watch.c b/kernel/audit_watch.c
> > > > > index 1255dbf..656c7e9 100644
> > > > > --- a/kernel/audit_watch.c
> > > > > +++ b/kernel/audit_watch.c
> > > > > @@ -540,8 +540,14 @@ int audit_dupe_exe(struct audit_krule *new, struct
> > > > > audit_krule *old)
> > > > >
> > > > > int audit_exe_compare(struct task_struct *tsk, struct
> > > > > audit_fsnotify_mark
> > > > >
> > > > > *mark) {
> > > > > - unsigned long ino = tsk->mm->exe_file->f_inode->i_ino;
> > > > > - dev_t dev = tsk->mm->exe_file->f_inode->i_sb->s_dev;
> > > > > -
> > > > > + struct file *exe_file;
> > > > > + unsigned long ino;
> > > > > + dev_t dev;
> > > > > +
> > > > > + rcu_read_lock();
> > > > > + exe_file = rcu_dereference(tsk->mm->exe_file);
> > > >
> > > > This line is triggering a sparse error on my system:
> > > > # make C=1 M=kernel
> > > > ...
> > > >
> > > > CHECK kernel/audit_watch.c
> > > >
> > > > kernel/audit_watch.c:548:20: error: incompatible types in comparison
> > > > expression (different address spaces)
> > >
> > > That's odd. I got this complaint when I had forgotten to add the
> > > rcu_dereference() call, but not in its current state. Mind you, I get
> > > swamped with errors and warnings from all over the system (starting with
> > > ptrace.c, signal.c, exit.c, fork.c, audit.c, ftrace.c,
> > > selinux/netnode.c, ...) when I add
> > > "M=kernel" to my build command, so I start to wonder how valid that
> > > result is or that flag. Where is M=kernel documented?
> >
> > I don't remember anymore, it's something I've been using so long that I've
> > forgotten where I first learned of it. The "M=<X>" flag signals that you only
> > want to build a specific module/directory, e.g. M=kernel builds everything
> > under kernel/ whereas M=security/selinux builds everything under
> > security/selinux.
> >
> > So you don't see this error?
>
> No, I don't, but I see a number of unrelated ones that I will address in time...
Do you plan to push this fix to next?
> > paul moore
>
> - RGB
- 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
next prev parent reply other threads:[~2015-08-12 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 14:20 [PATCH V10] fixup: audit: implement audit by executable Richard Guy Briggs
2015-08-10 16:22 ` Paul Moore
2015-08-10 17:29 ` Richard Guy Briggs
2015-08-10 18:43 ` Paul Moore
2015-08-11 4:15 ` Richard Guy Briggs
2015-08-12 9:48 ` Richard Guy Briggs [this message]
2015-08-12 14:21 ` Paul Moore
2015-08-12 15:19 ` Richard Guy Briggs
2015-08-13 2:30 ` 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=20150812094848.GA25337@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hda3.com \
--cc=pmoore@redhat.com \
--cc=sgrubb@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