All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bill O'Donnell" <billodo@sgi.com>
To: Chris Friedhoff <chris@friedhoff.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <jmorris@namei.org>,
	Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
	KaiGai Kohei <kaigai@kaigai.gr.jp>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH 1/1] security: introduce fs caps
Date: Mon, 13 Nov 2006 15:57:06 -0600	[thread overview]
Message-ID: <20061113215706.GA9658@sgi.com> (raw)
In-Reply-To: <20061109103349.e58e8f51.chris@friedhoff.org>

On Thu, Nov 09, 2006 at 10:33:49AM +0100, Chris Friedhoff wrote:
| Page http://www.friedhoff.org/fscaps.html updated ...
| Kernel 2.6.18.2 updated ...
| System keeps on humming ...
| Is anyone else using/testing the patch? Please give feedback ...

Most likely a cockpit error, but I'm having trouble when I give the 
capability to ping (using the userexample from your fscaps page):

$ uname -a
Linux certify 2.6.19-rc3 #3 SMP PREEMPT Mon Nov 13 14:40:54 CST 2006 ia64

$ sudo chmod 711 /bin/ping
$ ping -c 1 localhost
ping: icmp open socket: Operation not permitted

$ sudo setfcaps cap_net_raw=ep /bin/ping           
/bin/ping: Function not implemented (errno=38)

Any help is appreciated.

Bill

---
Bill O'Donnell
SGI
651.683.3079
billodo@sgi.com

  parent reply	other threads:[~2006-11-13 21:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 22:24 [PATCH 1/1] security: introduce fs caps Serge E. Hallyn
2006-11-08 22:48 ` Alexey Dobriyan
2006-11-08 23:52   ` Serge E. Hallyn
2006-11-09  5:27     ` Alexey Dobriyan
2006-11-09  6:17       ` Serge E. Hallyn
2006-11-13 16:43       ` Serge E. Hallyn
2006-11-13 21:04         ` Alexey Dobriyan
2006-11-14  3:01           ` Serge E. Hallyn
2006-11-09  6:10 ` Serge E. Hallyn
2006-11-09  9:33   ` Chris Friedhoff
2006-11-09 14:50     ` Bill O'Donnell
2006-11-13 21:57     ` Bill O'Donnell [this message]
2006-11-14  5:25       ` Serge E. Hallyn
2006-11-14 13:55         ` Bill O'Donnell
2006-11-14 15:23           ` Serge E. Hallyn
2006-11-14 17:28             ` Chris Friedhoff
2006-11-14 17:40               ` Bill O'Donnell
2006-11-15 12:08             ` KaiGai Kohei
2006-11-15 17:06               ` Bill O'Donnell
2006-11-15 21:49                 ` Chris Friedhoff
2006-11-16 14:47                   ` Bill O'Donnell
2006-11-17 18:37                     ` Chris Friedhoff
2006-11-17 19:12                     ` Chris Friedhoff
  -- strict thread matches above, loose matches on Subject: below --
2006-11-03 16:57 chris friedhoff
2006-11-03 20:00 ` Serge E. Hallyn
2006-11-03 20:29   ` Stephen Smalley
2006-11-03 20:47     ` Serge E. Hallyn
2006-11-04  2:08       ` Kyle Moffett
2006-11-04  4:12         ` James Morris
2006-11-06 13:31         ` Stephen Smalley
2006-09-06 18:27 Serge E. Hallyn
2006-09-06 20:51 ` Paul Jackson
2006-09-07  1:25   ` Serge E. Hallyn
2006-09-07  6:40     ` Paul Jackson

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=20061113215706.GA9658@sgi.com \
    --to=billodo@sgi.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=chris@friedhoff.org \
    --cc=chrisw@sous-sol.org \
    --cc=jmorris@namei.org \
    --cc=kaigai@kaigai.gr.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@us.ibm.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.