From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Richard Haines <richard_c_haines@btinternet.com>
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
Subject: Re: [PATCH V2] selinux: Add SCTP support
Date: Wed, 6 Dec 2017 10:46:38 -0200 [thread overview]
Message-ID: <20171206124638.GD3328@localhost.localdomain> (raw)
In-Reply-To: <20171206101736.3217-1-richard_c_haines@btinternet.com>
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 <richard_c_haines@btinternet.com>
> ---
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH V2] selinux: Add SCTP support
Date: Wed, 06 Dec 2017 12:46:38 +0000 [thread overview]
Message-ID: <20171206124638.GD3328@localhost.localdomain> (raw)
In-Reply-To: <20171206101736.3217-1-richard_c_haines@btinternet.com>
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 <richard_c_haines@btinternet.com>
> ---
> 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\x151198281817779&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
WARNING: multiple messages have this Message-ID (diff)
From: marcelo.leitner@gmail.com (Marcelo Ricardo Leitner)
To: linux-security-module@vger.kernel.org
Subject: [PATCH V2] selinux: Add SCTP support
Date: Wed, 6 Dec 2017 10:46:38 -0200 [thread overview]
Message-ID: <20171206124638.GD3328@localhost.localdomain> (raw)
In-Reply-To: <20171206101736.3217-1-richard_c_haines@btinternet.com>
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 <richard_c_haines@btinternet.com>
> ---
> 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
next prev parent reply other threads:[~2017-12-06 12:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 10:17 [PATCH V2] selinux: Add SCTP support Richard Haines
2017-12-06 10:17 ` Richard Haines
2017-12-06 10:17 ` Richard Haines
2017-12-06 12:46 ` Marcelo Ricardo Leitner [this message]
2017-12-06 12:46 ` Marcelo Ricardo Leitner
2017-12-06 12:46 ` Marcelo Ricardo Leitner
2017-12-06 14:15 ` Paul Moore
2017-12-06 14:15 ` Paul Moore
2017-12-06 14:15 ` Paul Moore
2017-12-06 20:13 ` David Miller
2017-12-06 20:13 ` David Miller
2017-12-06 20:13 ` David Miller
2017-12-07 23:37 ` Paul Moore
2017-12-07 23:37 ` Paul Moore
2017-12-07 23:37 ` 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=20171206124638.GD3328@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=eparis@parisplace.org \
--cc=linux-sctp@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyasevich@gmail.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.