From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:19212 "EHLO ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729225AbeJ2P6E (ORCPT ); Mon, 29 Oct 2018 11:58:04 -0400 Date: Mon, 29 Oct 2018 18:10:38 +1100 From: Dave Chinner Subject: Re: XFS: Hang and dmesg flood on mounting invalid FS image Message-ID: <20181029071038.GL19305@dastard> References: <20181029012058.GK19305@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Anatoly Trosinenko Cc: "Darrick J. Wong" , linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org On Mon, Oct 29, 2018 at 09:57:20AM +0300, Anatoly Trosinenko wrote: > > How did the corruption occur? > > It is a fuzzed image. Most probably, it was artificially "patched" by > fuzzer. Or do you mean "what particular bytes were changed"? I wondered how this specific corruption occurred in the real world. If i was a real world problem, it would have been indicative of a code bug if it did occur (i.e. whatever wrote the log record would have been broken) but seeing as it's a fuzzer problem, I don't need to look for any code bugs other than "we didn't validate the input properly". Cheers, Dave. -- Dave Chinner david@fromorbit.com