From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Ricardo Leitner Subject: Re: [PATCH V2] selinux: Add SCTP support Date: Wed, 6 Dec 2017 10:46:38 -0200 Message-ID: <20171206124638.GD3328@localhost.localdomain> References: <20171206101736.3217-1-richard_c_haines@btinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: selinux@tycho.nsa.gov, netdev@vger.kernel.org, linux-sctp@vger.kernel.org, linux-security-module@vger.kernel.org, paul@paul-moore.com, vyasevich@gmail.com, nhorman@tuxdriver.com, sds@tycho.nsa.gov, eparis@parisplace.org To: Richard Haines Return-path: Content-Disposition: inline In-Reply-To: <20171206101736.3217-1-richard_c_haines@btinternet.com> Sender: owner-linux-security-module@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, Dec 06, 2017 at 10:17:36AM +0000, Richard Haines wrote: > The SELinux SCTP implementation is explained in: > Documentation/security/SELinux-sctp.rst > > Signed-off-by: Richard Haines > --- > V2 Changes > Remove lock from selinux_sctp_assoc_request() > Fix selinux_sctp_sk_clone() kbuild test robot catch [1] > > [1] https://marc.info/?l=selinux&m=151198281817779&w=2 > Is this patchset going in via netdev tree or selinux one? I see Dave is tracking the v1 (http://patchwork.ozlabs.org/patch/841842/) so I'm thinking netdev but for netdev it would require a repost of the entire patchset, even if the first ones weren't changed. Marcelo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Ricardo Leitner Date: Wed, 06 Dec 2017 12:46:38 +0000 Subject: Re: [PATCH V2] selinux: Add SCTP support Message-Id: <20171206124638.GD3328@localhost.localdomain> List-Id: References: <20171206101736.3217-1-richard_c_haines@btinternet.com> In-Reply-To: <20171206101736.3217-1-richard_c_haines@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-security-module@vger.kernel.org On Wed, Dec 06, 2017 at 10:17:36AM +0000, Richard Haines wrote: > The SELinux SCTP implementation is explained in: > Documentation/security/SELinux-sctp.rst > > Signed-off-by: Richard Haines > --- > V2 Changes > Remove lock from selinux_sctp_assoc_request() > Fix selinux_sctp_sk_clone() kbuild test robot catch [1] > > [1] https://marc.info/?l=selinux&m1198281817779&w=2 > Is this patchset going in via netdev tree or selinux one? I see Dave is tracking the v1 (http://patchwork.ozlabs.org/patch/841842/) so I'm thinking netdev but for netdev it would require a repost of the entire patchset, even if the first ones weren't changed. Marcelo From mboxrd@z Thu Jan 1 00:00:00 1970 From: marcelo.leitner@gmail.com (Marcelo Ricardo Leitner) Date: Wed, 6 Dec 2017 10:46:38 -0200 Subject: [PATCH V2] selinux: Add SCTP support In-Reply-To: <20171206101736.3217-1-richard_c_haines@btinternet.com> References: <20171206101736.3217-1-richard_c_haines@btinternet.com> Message-ID: <20171206124638.GD3328@localhost.localdomain> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On Wed, Dec 06, 2017 at 10:17:36AM +0000, Richard Haines wrote: > The SELinux SCTP implementation is explained in: > Documentation/security/SELinux-sctp.rst > > Signed-off-by: Richard Haines > --- > V2 Changes > Remove lock from selinux_sctp_assoc_request() > Fix selinux_sctp_sk_clone() kbuild test robot catch [1] > > [1] https://marc.info/?l=selinux&m=151198281817779&w=2 > Is this patchset going in via netdev tree or selinux one? I see Dave is tracking the v1 (http://patchwork.ozlabs.org/patch/841842/) so I'm thinking netdev but for netdev it would require a repost of the entire patchset, even if the first ones weren't changed. Marcelo -- 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