From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 117A03857404 for ; Mon, 21 Mar 2022 17:30:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 117A03857404 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id EBB8F302FB81; Mon, 21 Mar 2022 18:30:10 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 3ACB1413CEB2; Mon, 21 Mar 2022 18:30:10 +0100 (CET) Message-ID: <40bb3499abf806bc56500eb3c74374bff421afe0.camel@klomp.org> Subject: Re: Some fuzzer workarounds From: Mark Wielaard To: Evgeny Vereshchagin Cc: david korczynski , elfutils-devel@sourceware.org Date: Mon, 21 Mar 2022 18:30:10 +0100 In-Reply-To: <542296A2-061F-41F6-9BB2-92871407E80F@ya.ru> References: <20220317133051.100876-1-mark@klomp.org> <741FAE40-F8E9-4DA7-A160-E30A76210AC8@ya.ru> <289F0554-4E5C-42F1-A3C9-773C828CA168@ya.ru> <542296A2-061F-41F6-9BB2-92871407E80F@ya.ru> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2022 17:30:15 -0000 Hi Evgeny, On Mon, 2022-03-21 at 17:33 +0300, Evgeny Vereshchagin wrote: > I tested the fuzz branch and I can confirm that all the issues > reported by OSS-Fuzz found with ASan+UBSan are gone. > I kind of lost track of them at some point but the following issues > can no longer be triggered: >=20 > fuzz-libdwfl-crashes/oss-fuzz-45629 \ > fuzz-libdwfl-crashes/oss-fuzz-45634 \ > fuzz-libdwfl-crashes/oss-fuzz-45635 \ > fuzz-libdwfl-crashes/oss-fuzz-45636 \ > fuzz-libdwfl-crashes/oss-fuzz-45646 \ > fuzz-libelf-crashes/oss-fuzz-45637 \ > fuzz-libelf-crashes/oss-fuzz-45682 Great. Thanks for testing. All patches from the fuzz branch are now merged. My local fuzzer also hasn't found any new issues for almost 24 hours now. > The unit tests have nothing to do with the fuzz branch because once I > pointed the tests to the master branch they also > failed. Looking at "phdr[8]: unknown object file note type 3405650558 > with owner name 'FDO' at offset 200" it seems > it's caused by the toolchain used there. On Fedora 35 the tests pass. Ah, oops. Yeah that is: https://systemd.io/COREDUMP_PACKAGE_METADATA/ https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects There are actually patches to properly recognize those. https://sourceware.org/pipermail/elfutils-devel/2021q4/thread.html#4375 I'll integrate those asap. Cheers, Mark