From nobody Tue Feb 14 21:06:01 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PGYdZ2nZyz3q09M for ; Tue, 14 Feb 2023 21:05:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PGYdY2rcYz43cx for ; Tue, 14 Feb 2023 21:05:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 31EL61GZ029000 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 14 Feb 2023 13:06:02 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 31EL61f4028999 for freebsd-arm@freebsd.org; Tue, 14 Feb 2023 13:06:01 -0800 (PST) (envelope-from fbsd) Date: Tue, 14 Feb 2023 13:06:01 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash) Message-ID: <20230214210601.GA28959@www.zefox.net> References: <20230212165333.GB19401@www.zefox.net> <20230212191308.GA21535@www.zefox.net> <20230212195324.GB21535@www.zefox.net> <03840D0B-13D4-4F22-BDAF-2887A4D78BED@yahoo.com> <20230213232519.GD95670@funkthat.com> <20230214161415.GA28276@www.zefox.net> <20230214183827.GG95670@funkthat.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230214183827.GG95670@funkthat.com> X-Spamd-Result: default: False [-1.10 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[zefox.net]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PGYdY2rcYz43cx X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Tue, Feb 14, 2023 at 10:38:27AM -0800, John-Mark Gurney wrote: > bob prohaska wrote this message on Tue, Feb 14, 2023 at 08:14 -0800: > > > > Is this a demonstration that the fsck segfault can be reproduced > > independtly of my particular corrupt filesystem? AFL is new to me. > > Yes, it is. It turns out that the FS to produce this failure is a LOT > smaller than I expected when compresed, I have included it later in the > email. The constant above was taken directly from the failing FS. > > AFL is a very useful tool, and found this crash and apparently 50+ > other crashes in only 5-10 minutes of running... I'll be investigating > a few of the other crashes as well, as fsck does ocassionally deal w/ > untrusted fs's. > Would trying to run fsck on the corrupt filesystem from an 8GB Pi4 (also running -current) make any difference? I.e., might more physical RAM cover up the bug and allow fsck to complete successfully? Is there a plain-English description of how AFL works? I gather it manipulates input read by a program to discover improperly handled cases, but even that is far from certain. There's no hope of me doing anything useful with AFL. I'm merely curious. Thanks very much for writing! bob prohaska