netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: casey@schaufler-ca.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	ext-jarkko.2.sakkinen@nokia.com, Janne.Karhunen@nokia.com,
	elena.reshetova@nokia.com
Subject: Re: [PATCH] net: provide capability and group sets via SCM
Date: Mon, 14 Feb 2011 17:49:19 -0800 (PST)	[thread overview]
Message-ID: <20110214.174919.48492611.davem@davemloft.net> (raw)
In-Reply-To: <4D51C38B.1060902@schaufler-ca.com>

From: Casey Schaufler <casey@schaufler-ca.com>
Date: Tue, 08 Feb 2011 14:28:27 -0800

> 
> Subject: [PATCH] net: provide group lists and capability set via CMSG
> 
> Provide the namespace converted group list of the peer
> process using the SCM mechanism. Provide the capability
> set of the peer process. The capability set is not
> namespace converted on the assumption that there is no
> such conversion available or required.
> 
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>

You can't just hit the asm-generic header, you have to also hit
all of the architectures that don't use the asm-generic header,
including sparc, powerpc, mips, s390, arm, alpha, cris, frv, h8300,
ia64, m32r, m68k, m68knommu, mn10300, parisc, and xtensa.

  reply	other threads:[~2011-02-15  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D3466BD.10500@schaufler-ca.com>
     [not found] ` <m1k4i1igzh.fsf@fess.ebiederm.org>
2011-01-19 14:57   ` [PATCH] scm: provide full privilege set via SCM_PRIVILEGE Casey Schaufler
2011-01-19 16:18     ` Eric W. Biederman
2011-01-19 20:40       ` Casey Schaufler
2011-02-08 22:28 ` [PATCH] net: provide capability and group sets via SCM Casey Schaufler
2011-02-15  1:49   ` David Miller [this message]
2011-02-15 18:09     ` Casey Schaufler

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=20110214.174919.48492611.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Janne.Karhunen@nokia.com \
    --cc=casey@schaufler-ca.com \
    --cc=elena.reshetova@nokia.com \
    --cc=ext-jarkko.2.sakkinen@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).