From: Paul Moore <pmoore@redhat.com>
To: Huw Davies <huw@codeweavers.com>
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 12/18] ipv6: Allow request socks to contain IPv6 options.
Date: Sun, 07 Feb 2016 14:56:11 -0500 [thread overview]
Message-ID: <2442064.Lu7DBv0u8O@sifl> (raw)
In-Reply-To: <1452246774-13241-13-git-send-email-huw@codeweavers.com>
On Friday, January 08, 2016 09:52:48 AM Huw Davies wrote:
> If set, these will that precedence over the parent's options during
^^^^
take
> both sending and child creation. If they're not set, the parent's
> options (if any) will be used.
>
> This is to allow the security_inet_conn_request() hook to modify the
> IPv6 options in just the same way that it already may do for IPv4.
>
> Signed-off-by: Huw Davies <huw@codeweavers.com>
> ---
> include/net/inet_sock.h | 7 ++++++-
> net/dccp/ipv6.c | 12 +++++++++---
> net/ipv4/tcp_input.c | 3 +++
> net/ipv6/tcp_ipv6.c | 12 +++++++++---
> 4 files changed, 27 insertions(+), 7 deletions(-)
--
paul moore
security @ redhat
prev parent reply other threads:[~2016-02-07 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 9:52 [RFC PATCH v2 12/18] ipv6: Allow request socks to contain IPv6 options Huw Davies
2016-02-07 19:56 ` Paul Moore [this message]
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=2442064.Lu7DBv0u8O@sifl \
--to=pmoore@redhat.com \
--cc=huw@codeweavers.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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).