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 53B023857C42 for ; Wed, 23 Mar 2022 00:35:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 53B023857C42 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 reform (deer0x09.wildebeest.org [172.31.17.139]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 59C9E302FB81; Wed, 23 Mar 2022 01:35:11 +0100 (CET) Received: by reform (Postfix, from userid 1000) id 167132E819FF; Wed, 23 Mar 2022 01:35:11 +0100 (CET) Date: Wed, 23 Mar 2022 01:35:11 +0100 From: Mark Wielaard To: Evgeny Vereshchagin Cc: david korczynski , elfutils-devel@sourceware.org Subject: Re: Some fuzzer workarounds Message-ID: References: <20220317133051.100876-1-mark@klomp.org> <741FAE40-F8E9-4DA7-A160-E30A76210AC8@ya.ru> <289F0554-4E5C-42F1-A3C9-773C828CA168@ya.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham 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: Wed, 23 Mar 2022 00:35:15 -0000 Hi Evgeny, On Tue, Mar 22, 2022 at 07:59:57PM +0300, Evgeny Vereshchagin wrote: > I can also prevent OSS-Fuzz from reporting new bugs found by MSan > by setting the experimental flag > > From https://google.github.io/oss-fuzz/getting-started/new-project-guide/#sanitizers > > If you want to test a particular sanitizer to see what crashes it generates > > without filing them in the issue tracker, you can set an experimental flag > > It should help to figure out whether it makes sense to keep it without spamming the mailing list > in the process. What do you think? I think that is a good idea. I really believe all the issues reported by MSAN are bogus. While the UBSAN and ASAN issues seem reasonable. At least I have a fix for the last one (45952 Misaligned-address in elf_cvt_gnuhash): https://sourceware.org/pipermail/elfutils-devel/2022q1/004782.html https://code.wildebeest.org/git/user/mjw/elfutils/commit/?h=fuzz Cheers, Mark