zip: Add patch fixing zipnote segfault
PATCH v4 1/1 zip: Add patch fixing zipnote segfault
This patch has been applied in several Linux distributions
--- .../zipnote-crashes-with-segfault.patch | 20 +++++++++++++++++++ meta/recipes-extended/zip/zip_3.0.bb | 1 + 2 files changed, 21 insertions(+) create mode 100644 meta/recipes-extended/zip/zip-3.0/zipnote-crashes-with-segfault.patch
meta/recipes-extended/zip/zip-3.0/zipnote-crashes-with-segfault.patch new file +20 -0
@@ -0,0 +1,20 @@ +Close the correct file descriptor + +https://bugs.archlinux.org/task/47713 + +Upstream-Status: Pending + +diff --git a/zipnote.c b/zipnote.c +index 5e02cb6..996f012 100644 +--- a/zipnote.c ++++ b/zipnote.c +@@ -661,7 +661,7 @@ char **argv; /* command line tokens */ + if ((r = zipcopy(z)) != ZE_OK) + ziperr(r, "was copying an entry"); + } +- fclose(x); ++ fclose(in_file); + + /* Write central directory and end of central directory with new comments */ + if ((c = zftello(y)) == (zoff_t)-1) /* get start of central */ +
meta/recipes-extended/zip/zip_3.0.bb +1 -0
@@ -12,6 +12,7 @@ S = "${WORKDIR}/zip30" SRC_URI = "${SOURCEFORGE_MIRROR}/infozip/Zip%203.x%20%28latest%29/3.0/zip30.tar.gz \ file://fix-security-format.patch \ file://10-remove-build-date.patch \ + file://zipnote-crashes-with-segfault.patch \ " UPSTREAM_VERSION_UNKNOWN = "1"
Signature · 1 line
2.17.2 (Apple Git-113)
✗ patchtest: failure for zip: Add patch fixing zipnote segfault (rev4)
== Series Details ==
Series: zip: Add patch fixing zipnote segfault (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/21894/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence]
Suggested fix Sign off the added patch file (meta/recipes-extended/zip/zip-3.0/zipnote-crashes-with-segfault.patch)
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe