From: David Miller <davem@davemloft.net>
To: acme@infradead.org
Cc: eparis@redhat.com, netdev@vger.kernel.org, nhorman@redhat.com,
dwalsh@redhat.com, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 2/3] net: pass kern to net_proto_family create function
Date: Thu, 05 Nov 2009 21:39:07 -0800 (PST) [thread overview]
Message-ID: <20091105.213907.235867065.davem@davemloft.net> (raw)
In-Reply-To: <20091105.210800.162780369.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Thu, 05 Nov 2009 21:08:00 -0800 (PST)
> From: Arnaldo Carvalho de Melo <acme@infradead.org>
> Date: Wed, 4 Nov 2009 15:31:47 -0200
>
>> Em Wed, Nov 04, 2009 at 11:32:17AM -0500, Eric Paris escreveu:
>>> The generic __sock_create function has a kern argument which allows the
>>> security system to make decisions based on if a socket is being created by
>>> the kernel or by userspace. This patch passes that flag to the
>>> net_proto_family specific create function, so it can do the same thing.
>>>
>>> Signed-off-by: Eric Paris <eparis@redhat.com>
>>
>> Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Applied to net-next-2.6
Eric, you missed Bluetooth and ATM in this change, breaking the build.
I'll fix this up, but next time...
next prev parent reply other threads:[~2009-11-06 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 16:32 [PATCH 1/3] net: drop capability from protocol definitions Eric Paris
2009-11-04 16:32 ` [PATCH 2/3] net: pass kern to net_proto_family create function Eric Paris
2009-11-04 16:54 ` Joe Perches
2009-11-04 17:31 ` Arnaldo Carvalho de Melo
2009-11-06 5:08 ` David Miller
2009-11-06 5:39 ` David Miller [this message]
2009-11-04 16:32 ` [PATCH 3/3] net: check kern before calling security subsystem Eric Paris
2009-11-04 17:32 ` Arnaldo Carvalho de Melo
2009-11-06 5:08 ` David Miller
2009-11-04 21:42 ` James Morris
2009-11-04 17:31 ` [PATCH 1/3] net: drop capability from protocol definitions Arnaldo Carvalho de Melo
2009-11-06 5:07 ` David Miller
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=20091105.213907.235867065.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@infradead.org \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.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.