From: Pascal Ouyang <Xin.Ouyang@windriver.com>
To: Xin Ouyang <xinpascal@gmail.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>, <eparis@redhat.com>,
<selinux@tycho.nsa.gov>
Subject: Re: [PATCH 20/25] libsemanage: Fallback_user_level can be NULL if you
Date: Thu, 12 Jan 2012 17:34:35 +0800 [thread overview]
Message-ID: <4F0EA92B.20400@windriver.com> (raw)
In-Reply-To: <4F0EA482.5050109@gmail.com>
Sorry. That should be "segfault still exists".
This patch could fix the segfault without
"0020-libsemanage-Fallback_user_level-can-be-NULL-if-you-a-1.patch".
Thanks.
- Pascal O.Y.
On 2012年01月12日 17:14, Xin Ouyang wrote:
> segfault still not exist.
>
> 1. Download and extract refpolicy-2.20110726.tar.bz2
> 2. cd refplicy && edit build.conf
> TYPE = standard
> ...
> 3. make conf && make policy && make load
> ...
> make: *** [load] Segmentation fault (core dumped)
>
>
> The attached patch will be OK. :)
>
> - Pascal O.Y.
>
>
> On 2011年12月20日 05:28, Daniel J Walsh wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> This patch looks good to me. acked.
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk7vrJEACgkQrlYvE4MpobP4ewCfUTl1JHSaXTpPtNUn1yJWDo1j
>> TMgAn0HPi8GRUqi8WdOugTGJReqXBKUV
>> =MQcr
>> -----END PGP SIGNATURE-----
>
--
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.
prev parent reply other threads:[~2012-01-12 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 21:28 [PATCH 20/25] libsemanage: Fallback_user_level can be NULL if you Daniel J Walsh
2012-01-12 9:14 ` Xin Ouyang
2012-01-12 9:34 ` Pascal Ouyang [this message]
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=4F0EA92B.20400@windriver.com \
--to=xin.ouyang@windriver.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=xinpascal@gmail.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.