From: Scott Matheina <scott@matheina.com>
To: Paul Moore <paul@paul-moore.com>
Cc: eparis@redhat.com, linux-audit@redhat.com,
linux-kernel@vger.kernel.org, trivial@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: Wed, 21 Oct 2015 19:35:20 -0500 [thread overview]
Message-ID: <56282F48.4090800@matheina.com> (raw)
In-Reply-To: <20081879.d8apxLOWgP@sifl>
On 10/21/2015 01:23 PM, Paul Moore wrote:
> On Sunday, October 18, 2015 12:50:45 PM 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:
>>>> Signed-off-by: Scott Matheina <scott@matheina.com>
>>>> ---
>>>>
>>>> kernel/auditfilter.c | 17 ++++++++++-------
>>>> 1 file changed, 10 insertions(+), 7 deletions(-)
>>> Sorry for the delay in reviewing this, comments inline ...
>>>
>>>> diff --git a/kernel/auditfilter.c b/kernel/auditfilter.c
>>>> index 7714d93..774f9ad 100644
>>>> --- a/kernel/auditfilter.c
>>>> +++ b/kernel/auditfilter.c
>>>> @@ -39,13 +39,13 @@
>>>>
>>>> * Locking model:
>>>> *
>>>>
>>>> * audit_filter_mutex:
>>>> - * Synchronizes writes and blocking reads of audit's filterlist
>>>> - * data. Rcu is used to traverse the filterlist and access
>>>> - * contents of structs audit_entry, audit_watch and opaque
>>>> - * LSM rules during filtering. If modified, these structures
>>>> - * must be copied and replace their counterparts in the filterlist.
>>>> - * An audit_parent struct is not accessed during filtering, so may
>>>> - * be written directly provided audit_filter_mutex is held.
>>>> + * Synchronizes writes and blocking reads of audit's filterlist
>>>> + * data. Rcu is used to traverse the filterlist and access
>>>> + * contents of structs audit_entry, audit_watch and opaque
>>>> + * LSM rules during filtering. If modified, these structures
>>>> + * must be copied and replace their counterparts in the filterlist.
>>>> + * An audit_parent struct is not accessed during filtering, so may
>>>> + * be written directly provided audit_filter_mutex is held.
>>>>
>>>> */
>>> Okay, that's fine.
> ...
>
>> As you might have guessed, this is one of my first patches. I wasn't sure if
>> a patch like this would even get reviewed, and responded to. I'm subscribed
>> to the linux-kernel mail group, and seeing what is acceptable.
>>
>> Thanks for the review. I don't plan on making a habit of submitting such
>> incredibly trivial patches, but you have to start somewhere, and I thought
>> it'd be hard to screw up by fixing a couple of trivial style errors.
> We all start somewhere, and with that in mind, if you want to resubmit this
> patch with only the fix above (fixing the whitespace in the comment block),
> I'll apply it. While the patch is trivial, it is does fix a minor nit with
> near-zero risk.
>
> I would encourage you to try something a bit more substantial next time, as
> they say, bug fixes are the quickest way to a maintainer's heart.
>
Thanks for the feedback. I'll resubmit. Now I get to figure out how to resubmit a patch with changes, so a good
learning experience for me. Pure Hobbyist at this time, but I love to learn.
Scott
next prev parent reply other threads:[~2015-10-22 0:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 1:57 [PATCH 2/2] Fixed Trivial Warnings in file: Deleted Spaces prior to tabs, and added lines. modified: kernel/auditfilter.c 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
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 [this message]
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=56282F48.4090800@matheina.com \
--to=scott@matheina.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.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;
as well as URLs for NNTP newsgroup(s).