From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BFF7830F82 for ; Thu, 19 Oct 2023 17:05:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="G7NnErs6" Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B32EC130; Thu, 19 Oct 2023 10:05:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1697735130; x=1729271130; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=SvRT6LTSrzS+ByQI2jQdeZOuYjcngLGwBF4+TKTOda0=; b=G7NnErs6GaEDfqZfERWKHcS3qcKgvT/+Q4D+A/SpSM4AKbc01PTCkTJz kMa95aZmx2gOmQwgb+WUYN8hIXeQZ3PG8VfSHkPDI39INIaVtoTmzg5NB VRV/5qV6YZcJyUh7kwcADUIUrtnr9mljugxslJqmNj2dRvNeYw7qB0xw4 imAV+IKHwcyCuV4h8fVwC7tg87SZI/GHc/43XVWCi696SO7b4dAn7JW+q rEl3BMeZt/nw0pnFGJfIPQMxPrsH3WSOjysCGUiWJaJqavxsiWJxRenDL 4qMohFI00DSVI6FNjZriy2L1OEsv0CichDXd85pi4L4m78KFYHB8CuGCK g==; X-IronPort-AV: E=McAfee;i="6600,9927,10868"; a="376691831" X-IronPort-AV: E=Sophos;i="6.03,237,1694761200"; d="scan'208";a="376691831" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Oct 2023 10:05:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10868"; a="880746237" X-IronPort-AV: E=Sophos;i="6.03,237,1694761200"; d="scan'208";a="880746237" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga004.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Oct 2023 10:05:23 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97-RC2) (envelope-from ) id 1qtWSW-00000006w92-1Z6p; Thu, 19 Oct 2023 20:05:20 +0300 Date: Thu, 19 Oct 2023 20:05:20 +0300 From: Andy Shevchenko To: Josh Poimboeuf Cc: Jan Kara , Nathan Chancellor , Nick Desaulniers , Kees Cook , Ferry Toth , Linus Torvalds , linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org Subject: Re: [GIT PULL] ext2, quota, and udf fixes for 6.6-rc1 Message-ID: References: <20231018184613.tphd3grenbxwgy2v@quack3> <20231019101854.yb5gurasxgbdtui5@quack3> <20231019164240.lhg5jotsh6vfuy67@treble> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20231019164240.lhg5jotsh6vfuy67@treble> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Thu, Oct 19, 2023 at 09:42:40AM -0700, Josh Poimboeuf wrote: > On Thu, Oct 19, 2023 at 05:44:30PM +0300, Andy Shevchenko wrote: > > So, what I have done so far. > > 1) I have cleaned ccaches and stuff as I used it to avoid collisions; > > 2) I have confirmed that CONFIG_DEBUG_LIST affects boot, the repo > > I'm using is published here [0][1]; > > 3) reverted quota patches until before this merge ([2] - last patch), > > still boots; > > 4) reverted disabling of CONFIG_DEBUG_LIST [2], doesn't boot; > > 5) okay, rebased on top of merge, i.e. 1500e7e0726e, with DEBUG_LIST [3], > > doesn't boot; > > 6) rebased [3] on one merge before, i.e. 63580f669d7f [4], voilą -- it boots!; > > > > And (tadaam!) I have had an idea for a while to replace GCC with LLVM > > (at least for this test), so [0] boots as well! > > > > So, this merge triggered a bug in GCC, seems like... And it's _the_ merge > > commit, which is so-o weird! > > I'm not really a compiler person, but IMO it's highly unlikely to be a > GCC bug unless you can point to the bad code generation. Hmm... Then what's the difference between clang and GCC on the very same source code? One of them has a bug in my opinion. > If CONFIG_DEBUG_LIST is triggering it, it's most likely some kind of > memory corruption, in which case seemingly random events can trigger the > detection of it (or lack thereof). Note disabling QUOTA has the same effect, so if it's a corruption it happens somewhere there. > Any chance it boots with the following? Nope, no luck. -- With Best Regards, Andy Shevchenko