From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@osdl.org>, "Serge E. Hallyn" <serue@us.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: capabilities-introduce-per-process-capability-bounding-set.patch breaks FC6 Avahi
Date: Fri, 30 Nov 2007 14:41:34 -0500 [thread overview]
Message-ID: <20071130194134.GA7536@c2.user-mode-linux.org> (raw)
avahi-daemon fails to start on FC6 when
capabilities-introduce-per-process-capability-bounding-set.patch is
applied.
strace shows
capset(0x19980330, 0, {CAP_SETGID|CAP_SETUID|CAP_SYS_CHROOT, CAP_SETGID|CAP_SETUID|CAP_SYS_CHROOT, 0}) = -1 EPERM (Operation not permitted)
I don't know if this is expected, but the changelog doesn't seem to
imply that this will break things.
Jeff
--
Work email - jdike at linux dot intel dot com
next reply other threads:[~2007-11-30 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 19:41 Jeff Dike [this message]
2007-11-30 22:29 ` capabilities-introduce-per-process-capability-bounding-set.patch breaks FC6 Avahi Jiri Slaby
2007-12-01 0:21 ` Jeff Dike
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=20071130194134.GA7536@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).