All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: "Todd Miller" <Tmiller@tresys.com>
Cc: "Joshua Brindle" <method@manicmethod.com>, selinux@tycho.nsa.gov
Subject: Re: PATCH: peersid capability support
Date: Fri, 30 Nov 2007 13:19:55 -0500	[thread overview]
Message-ID: <200711301319.55735.paul.moore@hp.com> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B0158801455A30@exchange.columbia.tresys.com>

On Friday 30 November 2007 11:59:54 am Todd Miller wrote:
> Paul Moore wrote:
> > On Friday 30 November 2007 9:43:29 am Joshua Brindle wrote:
> >> Aside from this issue have you tried the patch against your kernel
> >> patches? We did not test with your kernel, we inspected the policy
> >> manually to ensure the ebitmap was set up correctly.
> >
> > Help?  What is this patch backed against?
>
> They are based on selinux trunk.  You do not want Josh's original diffs
> applied as the new diffs are meant to supercede Josh's.  I just svn up'd
> to rev 2692 and verified that they still apply.

Okay, that's what I thought but when I tried applying just your patch it 
wouldn't apply so I tried applying Josh's patches first.

> > I have a fresh copy of the SVN sources and I get a ton of failures
> > applying just this patch.  If I go back and apply Josh's original two
> > patches then try applying Todd's patch I still get failures, although
> > there are less of them.
>
> I don't know why that would be.  I have verified that the patch that
> arrived via the list didn't get munged in transit.

Okay, well maybe I'm doing something stupid but the patch appears to modify 
two files which do not exist in my SVN tree ...

 * trunk/libsepol/include/sepol/policydb/polcaps.h
 * trunk/libsepol/src/polcaps.c

The rest of the patch appears to apply just fine.

-- 
paul moore
linux security @ hp

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2007-11-30 18:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 19:27 PATCH: peersid capability support tmiller
2007-11-29 21:24 ` Stephen Smalley
2007-11-29 23:24   ` Joshua Brindle
2007-11-30 13:34     ` Stephen Smalley
2007-11-30 14:38       ` Joshua Brindle
2007-11-30 14:48         ` Stephen Smalley
2007-11-30 14:53           ` Stephen Smalley
2007-11-30 15:31           ` Joshua Brindle
2007-11-30 15:44             ` Paul Moore
2007-11-30 16:02               ` Joshua Brindle
2007-11-30 16:19                 ` Paul Moore
2007-11-30 16:12             ` Stephen Smalley
2007-11-30 16:41               ` Stephen Smalley
2007-11-30 14:29   ` Paul Moore
2007-11-30 14:43     ` Joshua Brindle
2007-11-30 14:47       ` Paul Moore
2007-11-30 16:30       ` Paul Moore
2007-11-30 16:59         ` Todd Miller
2007-11-30 17:08           ` Stephen Smalley
2007-11-30 18:19           ` Paul Moore [this message]
2007-12-03 15:53     ` Christopher J. PeBenito
2008-01-03 15:15 ` Václav Ovsík
2008-01-03 15:25   ` Todd Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-11-30 17:34 Todd C. Miller
2007-11-30 19:06 ` Paul Moore
2007-11-30 22:48   ` Paul Moore
2007-12-01  0:19     ` Joshua Brindle
2007-12-03 17:32       ` Paul Moore
2007-12-03 18:21         ` Stephen Smalley
2007-12-03 19:41 Todd C. Miller
2007-12-04 19:26 ` Paul Moore
2007-12-04 20:18   ` Stephen Smalley
2007-12-05 18:58 ` Stephen Smalley
2007-12-05 19:00   ` Todd 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=200711301319.55735.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=Tmiller@tresys.com \
    --cc=method@manicmethod.com \
    --cc=selinux@tycho.nsa.gov \
    /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.