From: "Amit Shah" <shahamit@gmail.com>
To: "Stephen Smalley" <sds@tycho.nsa.gov>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
"Andrew Morgan" <morgan@kernel.org>
Subject: Re: [Bugme-new] [Bug 10748] New: dhclient fails to run; capabilities error
Date: Tue, 20 May 2008 19:37:03 +0530 [thread overview]
Message-ID: <877aabc40805200707uf2bd4d8k5d82ee7c9beeb7a5@mail.gmail.com> (raw)
In-Reply-To: <1211291902.7486.121.camel@moss-spartans.epoch.ncsc.mil>
On Tue, May 20, 2008 at 7:28 PM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> On Tue, 2008-05-20 at 09:38 -0400, Stephen Smalley wrote:
>> Which means that he is using the dummy security module.
>> And it appears that a prior commit moved KEEPCAPS handling from
>> core prctl() to cap_task_prctl(), but didn't replicate it in
>> the dummy_task_prctl().
>>
>> The dummy module really needs to die.
>
> Question for the bug reporter: did you really mean to build a kernel
> without capabilities support? Surprise! They don't really work when
> disabled.
No; I was just trying out some random configs. This config worked till
.25 properly though.
--
Amit Shah
http://www.amitshah.net/
next prev parent reply other threads:[~2008-05-20 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10748-10286@http.bugzilla.kernel.org/>
2008-05-19 18:28 ` [Bugme-new] [Bug 10748] New: dhclient fails to run; capabilities error Andrew Morton
2008-05-20 13:48 ` Amit Shah
2008-05-20 13:49 ` Serge E. Hallyn
2008-05-20 13:38 ` Stephen Smalley
2008-05-20 13:58 ` Stephen Smalley
2008-05-20 14:07 ` Amit Shah [this message]
2008-05-20 14:45 ` Stephen Smalley
2008-05-20 15:06 ` Stephen Smalley
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=877aabc40805200707uf2bd4d8k5d82ee7c9beeb7a5@mail.gmail.com \
--to=shahamit@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=morgan@kernel.org \
--cc=netdev@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 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).