From: James Morris <jmorris@namei.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Dan Carpenter <dan.carpenter@oracle.com>,
Markus Elfring <elfring@users.sourceforge.net>,
Eric Paris <eparis@parisplace.org>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
William Roberts <william.c.roberts@intel.com>,
selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] selinux: Fix an uninitialized variable bug
Date: Tue, 4 Apr 2017 10:03:42 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1704040949430.16760@namei.org> (raw)
In-Reply-To: <CAHC9VhQHabPm08bjXgw+nx6X7c6bsBeOc1ZXLFM58nVrWzsh7g@mail.gmail.com>
On Mon, 3 Apr 2017, Paul Moore wrote:
> James, I know you don't track SELinux development very closely so I'm
> going to give you the benefit of the doubt and assume you haven't
> already seen my responses to Markus in his 46 patch thread. If you
> did follow the thread you would have noticed that I rejected several
> of his patches as only adding noise/churn, and several more due to
> personal preference; those that I did merge, I did review. I review
> every patch that I merge, even the patches from Stephen.
I did see the thread, and my email came across as critical of you, which
was not my intention. I do certainly trust your skill and judgement.
- James
--
James Morris
<jmorris@namei.org>
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] selinux: Fix an uninitialized variable bug
Date: Tue, 04 Apr 2017 00:03:42 +0000 [thread overview]
Message-ID: <alpine.LRH.2.20.1704040949430.16760@namei.org> (raw)
In-Reply-To: <CAHC9VhQHabPm08bjXgw+nx6X7c6bsBeOc1ZXLFM58nVrWzsh7g@mail.gmail.com>
On Mon, 3 Apr 2017, Paul Moore wrote:
> James, I know you don't track SELinux development very closely so I'm
> going to give you the benefit of the doubt and assume you haven't
> already seen my responses to Markus in his 46 patch thread. If you
> did follow the thread you would have noticed that I rejected several
> of his patches as only adding noise/churn, and several more due to
> personal preference; those that I did merge, I did review. I review
> every patch that I merge, even the patches from Stephen.
I did see the thread, and my email came across as critical of you, which
was not my intention. I do certainly trust your skill and judgement.
- James
--
James Morris
<jmorris@namei.org>
WARNING: multiple messages have this Message-ID (diff)
From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] selinux: Fix an uninitialized variable bug
Date: Tue, 4 Apr 2017 10:03:42 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1704040949430.16760@namei.org> (raw)
In-Reply-To: <CAHC9VhQHabPm08bjXgw+nx6X7c6bsBeOc1ZXLFM58nVrWzsh7g@mail.gmail.com>
On Mon, 3 Apr 2017, Paul Moore wrote:
> James, I know you don't track SELinux development very closely so I'm
> going to give you the benefit of the doubt and assume you haven't
> already seen my responses to Markus in his 46 patch thread. If you
> did follow the thread you would have noticed that I rejected several
> of his patches as only adding noise/churn, and several more due to
> personal preference; those that I did merge, I did review. I review
> every patch that I merge, even the patches from Stephen.
I did see the thread, and my email came across as critical of you, which
was not my intention. I do certainly trust your skill and judgement.
- James
--
James Morris
<jmorris@namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-04-04 0:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 15:21 [PATCH] selinux: Fix an uninitialized variable bug Dan Carpenter
2017-03-31 15:21 ` Dan Carpenter
2017-03-31 15:21 ` Dan Carpenter
2017-03-31 15:52 ` Stephen Smalley
2017-03-31 15:52 ` Stephen Smalley
2017-03-31 15:52 ` Stephen Smalley
2017-03-31 19:18 ` Paul Moore
2017-03-31 19:18 ` Paul Moore
2017-03-31 19:18 ` Paul Moore
2017-04-01 6:40 ` selinux: Fix an uninitialized variable bug in range_read() SF Markus Elfring
2017-04-01 6:40 ` SF Markus Elfring
2017-04-01 6:40 ` SF Markus Elfring
2017-04-01 14:52 ` Paul Moore
2017-04-01 14:52 ` Paul Moore
2017-04-01 14:52 ` Paul Moore
2017-04-03 1:10 ` [PATCH] selinux: Fix an uninitialized variable bug James Morris
2017-04-03 1:10 ` James Morris
2017-04-03 1:10 ` James Morris
2017-04-03 21:45 ` Paul Moore
2017-04-03 21:45 ` Paul Moore
2017-04-03 21:45 ` Paul Moore
2017-04-04 0:03 ` James Morris [this message]
2017-04-04 0:03 ` James Morris
2017-04-04 0:03 ` James Morris
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=alpine.LRH.2.20.1704040949430.16760@namei.org \
--to=jmorris@namei.org \
--cc=dan.carpenter@oracle.com \
--cc=elfring@users.sourceforge.net \
--cc=eparis@parisplace.org \
--cc=james.l.morris@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=william.c.roberts@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.