From: Eric Paris <eparis@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>,
Casey Schaufler <casey@schaufler-ca.com>,
selinux@tycho.nsa.gov, jmorris@namei.org
Subject: Re: [PATCH 4/4] SELinux: allow userspace to read policy back out of the kernel
Date: Wed, 16 Jun 2010 12:58:41 -0400 [thread overview]
Message-ID: <1276707521.2749.52.camel@localhost> (raw)
In-Reply-To: <1276706472.17827.35.camel@moss-pluto.epoch.ncsc.mil>
On Wed, 2010-06-16 at 12:41 -0400, Stephen Smalley wrote:
> On Wed, 2010-06-16 at 11:26 -0400, Eric Paris wrote:
> > No question wrapping my head around the new ebitmap format was the tough
> > part. I added printk's to display every ebitmap and node as it was read
> > in and as I wrote them out. Got the same thing for the couple thousand
> > lines I could show in dmesg, so I think I'm ok there.
> >
> > I was trying to use gdb yesterday to figure out what was wrong, but
> > could get the darn thing to break where I wanted it to. I'll debug like
> > I'm used to (in the kernel) and see what I did....
>
> Oh, I found it. mls_write_level() in your patch sets buf[1] rather than
> buf[0] and then writes buf[0].
/me feels like the compiler should have been able to find that
particular one....
--
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.
next prev parent reply other threads:[~2010-06-16 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 16:37 [PATCH 1/4] SELinux: seperate range transition rules to a seperate function Eric Paris
2010-06-11 16:37 ` [PATCH 2/4] SELinux: move genfs read to a separate function Eric Paris
2010-06-16 14:18 ` Stephen Smalley
2010-06-16 14:24 ` Stephen Smalley
2010-06-11 16:37 ` [PATCH 3/4] SELinux: break ocontext reading into " Eric Paris
2010-06-16 14:39 ` Stephen Smalley
2010-06-11 16:37 ` [PATCH 4/4] SELinux: allow userspace to read policy back out of the kernel Eric Paris
2010-06-14 14:48 ` Stephen Smalley
2010-06-14 15:12 ` Eric Paris
2010-06-15 4:42 ` Casey Schaufler
2010-06-15 14:33 ` Eric Paris
2010-06-16 14:53 ` Stephen Smalley
2010-06-16 15:26 ` Eric Paris
2010-06-16 16:41 ` Stephen Smalley
2010-06-16 16:58 ` Eric Paris [this message]
2010-06-17 7:26 ` KaiGai Kohei
2010-06-17 14:51 ` Eric Paris
2010-06-14 14:57 ` Stephen Smalley
2010-06-14 14:59 ` Stephen Smalley
2010-06-14 15:24 ` Eric Paris
2010-06-14 16:14 ` Stephen Smalley
2010-06-14 17:55 ` Eric Paris
2010-06-14 18:04 ` Stephen Smalley
2010-06-18 12:01 ` Christopher J. PeBenito
2010-06-16 13:02 ` [PATCH 1/4] SELinux: seperate range transition rules to a seperate function Stephen Smalley
2010-06-17 5:02 ` James Morris
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=1276707521.2749.52.camel@localhost \
--to=eparis@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=kaigai@kaigai.gr.jp \
--cc=sds@tycho.nsa.gov \
--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.