mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: Scott Matheina <scott@matheina.com>
Cc: Joe Perches <joe@perches.com>, Paul Moore <paul@paul-moore.com>,
	linux-audit@redhat.com, trivial@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Fixed Trivial Warnings in file: Deleted Spaces prior to tabs, and added lines. modified: kernel/auditfilter.c
Date: Thu, 22 Oct 2015 08:53:25 -0400	[thread overview]
Message-ID: <20151022125325.GA16212@madcap2.tricolour.ca> (raw)
In-Reply-To: <562857B2.4070408@matheina.com>

On 15/10/21, Scott Matheina wrote:
> On 10/21/2015 09:15 PM, Richard Guy Briggs wrote:
> > On 15/10/21, Scott Matheina wrote:
> >> On 10/21/2015 10:33 AM, Richard Guy Briggs wrote:
> >>> On 15/10/21, Joe Perches wrote:
> >>>> On Mon, 2015-10-19 at 12:10 -0400, Richard Guy Briggs wrote:
> >>>>> On 15/10/18, Scott Matheina wrote:
> >>>>>> On 10/14/2015 04:54 PM, Paul Moore wrote:
> >>>>>>> On Saturday, October 10, 2015 08:57:55 PM Scott Matheina wrote:
> >>>> []
> >>>>>>>> diff --git a/kernel/auditfilter.c b/kernel/auditfilter.c
> >>>> []
> >>>>>>>> @@ -109,6 +109,7 @@ void audit_free_rule_rcu(struct rcu_head *head)
> >>>>>>>>  {
> >>>>>>>>  	struct audit_entry *e = container_of(head, struct audit_entry, rcu);
> >>>>>>>>  	audit_free_rule(e);
> >>>>>>>> +
> >>>>>>>>  }
> >>>>>>> Why?
> >>>>>> I was following the error messages in checkpatch.pl, but the warning
> >>>>>> went away after adding this line. No problem with the code. 
> >>>>> That sounds like a bug in checkpatch.pl, since that blank line should be
> >>>>> tween the declaration and the function call.
> >>>> checkpatch message asks for a blank line after the
> >>>> "struct audit_entry *e = ..." declaration.
> >>> Well then maybe it is a bug in his interpretation of the output of
> >>> checkpatch.pl?  Scott, did you re-run checkpatch.pl after adding those
> >>> spaces?  Did it pass?
> >> The error did go away. 
> > Joe, I confirm the error went away.  Looks like a bug in checkpatch.pl
> > to me.  I tried a number of combinations of things and it didn't
> > complain about several things it should have.  I did try a few other
> > things to make sure it was still finding problems like brace placement
> > and leading spaces, but it looks like the blank line checking code isn't
> > working.  This is on 4.0, so maybe it has been fixed since then.  Scott,
> > what kernel version are you using?
> I'm running Ubuntu 14.04 LTS (Kernel 3.19.0-30-generic) on my machine.
> 
> I cloned Linus' repo for source code. I'm pretty sure you were talking
> about the active Kernel on my machine, so if not please let me know.

I was talking about the source used to generate this patch in question,
run ./scripts/checkpatch.pl and do a compile test.  The active kernel on
your machine is irrelevant unless you subsequently booted it to test it.
How recent is your clone/pull of Linus' repo?

> >>>>>>>>  	while (*list != ~0U) {
> >>>>>>>> +
> >>>>>>>>  		unsigned n = *list++;
> >>>>>>>>  		if (n >= AUDIT_BITMASK_SIZE * 32 - AUDIT_SYSCALL_CLASSES) {
> >>>>>>>>  			kfree(p);
> >>>>>>> Why?
> >>>>>> This is the same as above. Just going through the checkpatch.pl
> >>>>>> script, and looking for warnings to fix. 
> >>>>> Again, another manifestation of that bug?  That blank line should be
> >>>>> after the declaration and before the if statement.
> >>>> []
> >>>>> Well, I agree, you have to start somewhere...  Too bad you hit a bug in
> >>>>> checkpatch.pl!
> >>>> Here too, not a bug in checkpatch.
> >>>>
> >>>> checkpatch output asks for a blank line after the
> >>>> "unsigned n" declaration, not before.
> >>> - RGB
> > - 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

  reply	other threads:[~2015-10-22 12:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  1:57 Scott Matheina
2015-10-14 21:54 ` Paul Moore
2015-10-18 17:50   ` Scott Matheina
2015-10-19 16:10     ` Richard Guy Briggs
2015-10-21 13:58       ` Joe Perches
2015-10-21 15:33         ` Richard Guy Briggs
2015-10-22  0:30           ` Scott Matheina
2015-10-22  2:15             ` Richard Guy Briggs
2015-10-22  3:27               ` Scott Matheina
2015-10-22 12:53                 ` Richard Guy Briggs [this message]
2015-10-25 23:53               ` Scott Matheina
2015-10-27 19:54               ` Joe Perches
2015-10-21 18:23     ` Paul Moore
2015-10-22  0:35       ` Scott Matheina
2015-10-22 20:47         ` 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=20151022125325.GA16212@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=scott@matheina.com \
    --cc=trivial@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

all inboxes | Powered by JetHome®