From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Fix libxml2 unsafe memory access
Date: Wed, 28 Oct 2015 13:22:52 +0800 [thread overview]
Message-ID: <cover.1446009435.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The patch is from:
https://bugzilla.gnome.org/show_bug.cgi?id=746048
Build image with packagegroup-core-buildessential, boot the image and compile following c code:
==================================================
#include "string.h"
#include <libxml/HTMLparser.h>
#include <libxml/HTMLtree.h>
int main(int argc, char** argv)
{
// Nokogiri::HTML::fragment("<!-- ")
htmlDocPtr doc ;
int options = HTML_PARSE_RECOVER | HTML_PARSE_NOERROR | HTML_PARSE_NOWARNING | HTML_PARSE_NONET ;
char* HTMLFRAG_GOOD = "<html><body><!-- x" ;
char* HTMLFRAG_BAD = "<html><body><!--" ;
char* HTMLFRAG = HTMLFRAG_BAD ;
xmlInitParser();
doc = htmlReadMemory(HTMLFRAG, strlen(HTMLFRAG),
NULL,
"UTF-8",
options);
xmlFreeDoc(doc);
}
==================================================
Run with valgrind, there is no warning.
The following changes since commit 8a0d8eee432924433c3e70198aaeab3161476c5f:
toaster manual: Updated the set up and use chapter (2015-10-27 07:28:22 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib kangkai/libxml2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=kangkai/libxml2
Kai Kang (1):
libxml2: fix unsafe memory access
.../libxml2/libxml2-fix-unsafe-memory-access.patch | 97 ++++++++++++++++++++++
meta/recipes-core/libxml/libxml2_2.9.2.bb | 3 +-
2 files changed, 99 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-core/libxml/libxml2/libxml2-fix-unsafe-memory-access.patch
--
2.6.1
next reply other threads:[~2015-10-28 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 5:22 kai.kang [this message]
2015-10-28 5:22 ` [PATCH 1/1] libxml2: fix unsafe memory access kai.kang
2015-10-28 9:41 ` Jussi Kukkonen
2015-10-28 10:12 ` Kang Kai
2015-10-28 10:55 ` Alexander Kanavin
2015-10-28 11:15 ` Burton, Ross
2015-10-29 1:43 ` Kang Kai
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=cover.1446009435.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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.