Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp1779284rwd; Tue, 13 Jun 2023 14:12:28 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4slzY5iHKasRPtbxMzG5VanzxnVEEVvRDE1J8zwfMDEPUtl3dqycT7TLsRqOZHUiZu3/9a X-Received: by 2002:a17:907:9445:b0:982:227e:1a15 with SMTP id dl5-20020a170907944500b00982227e1a15mr5866877ejc.2.1686690747764; Tue, 13 Jun 2023 14:12:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686690747; cv=none; d=google.com; s=arc-20160816; b=Pd/h3t8WipFUr5XczFEyD4LRswvMCMXY6fz0sEfJR0ajUQYfQASt9iVS56kM2MV8Th yWKolCvcyIX9fJ3JFVMTzvOEJQBBaxDnIu3TD09nVZSjQgUn8Ind1VfwhqRMSZCFN3GR bSe4wSK0PciEqRp+uVZ8893nbcfBoHuZG2ZlXQ4Bd9g+VrayvedRSB3CfGuvDv2m4Z0J dg2zZthROKzt+eTdUC71wJQjY1UNZaEgjQ1koG3GnXUYhr99vp+ZCOSEpzbdy8lxnwJO Hzh/1qnR7q6QDhl9IoZrSNPajF1+01FzkIkkVhNDrTXOevy3zgskb2nK1awBZ99iky+g /dsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=KeeAwDWlJRVDgPH4ESSSQsshzln+Tcs4Eg9NmhQztj0=; b=CDi4c+u4Ddeq2Gjb+B54B/cpVeOgh3Hd0/QGjB8LvVG57zV+vtx4aPeb1EFTw9IpFU 3KFP2TF6rj+wLzdN1zp/b1qDTGyH1hoNe5ZEazBNc2aVVYYna7hTs55Jr+rYghk4Z20l Iq/qzazaf9HRN6GVx7s0tv583p20l81f0BVVxxZoYgidiEdw+hi/RVCAw7kZZq7DRaex 45ArMqTHHjeiLi8Le2Gu5TZhNb8522nwyW22tLLJJ8lT63Jrg7Phb2A8w5rqdtJKuUGj 4gQRJEdl3cXcsqaCcWpQKTf8NFTU4OSpiGcljxKWCmSQpgERwUlegJ+T7pcY2PY4OzO8 t86Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=tmuJkO+0; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519 header.b=z83TiQWb; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l20-20020a170906079400b0097885f7cce8si7190462ejc.972.2023.06.13.14.12.00; Tue, 13 Jun 2023 14:12:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=tmuJkO+0; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519 header.b=z83TiQWb; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232949AbjFMVFi (ORCPT + 99 others); Tue, 13 Jun 2023 17:05:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239175AbjFMVFc (ORCPT ); Tue, 13 Jun 2023 17:05:32 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 58E1F1FC1 for ; Tue, 13 Jun 2023 14:05:28 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 07B551FDD9; Tue, 13 Jun 2023 21:05:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1686690327; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KeeAwDWlJRVDgPH4ESSSQsshzln+Tcs4Eg9NmhQztj0=; b=tmuJkO+06jtVn3N1M68T4Dgd2nu7GIkGxCPqYFsCM+ZntDbPY0SwqaAAHYDejhcmtFrQra 8Prcr5V1IENGhubSKNnZ0p3sPBbgcy6doDSKag4yQHwfBYWWh/C0i55/ykNqeyJBgbN114 GkDBj7G0PI9K0ZAJymPbJ3FxiZb86rA= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1686690327; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KeeAwDWlJRVDgPH4ESSSQsshzln+Tcs4Eg9NmhQztj0=; b=z83TiQWbpgQ/Eae4+cVYzr8nyCcnFOwtDzYQponsH0C4btJftfw4yrrZ68UTAfdHNUuEVg kslgjniMD0jx9/Aw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id EDAD813345; Tue, 13 Jun 2023 21:05:26 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Wd37ORbaiGTqMQAAMHmgww (envelope-from ); Tue, 13 Jun 2023 21:05:26 +0000 Received: by quack3.suse.cz (Postfix, from userid 1000) id 7B380A0755; Tue, 13 Jun 2023 23:05:26 +0200 (CEST) Date: Tue, 13 Jun 2023 23:05:26 +0200 From: Jan Kara To: Theodore Ts'o Cc: Aleksandr Nogikh , adilger.kernel@dilger.ca, jack@suse.com, linux-ext4@vger.kernel.org, syzkaller-bugs@googlegroups.com, syzbot Subject: Re: [syzbot] [ext4?] UBSAN: shift-out-of-bounds in ext2_fill_super (2) Message-ID: <20230613210526.ivz72esveqwrbwsr@quack3> References: <00000000000079134b05fdf78048@google.com> <20230613180103.GC18303@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230613180103.GC18303@mit.edu> X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_SOFTFAIL,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue 13-06-23 14:01:03, Theodore Ts'o wrote: > I wonder if we should have a separate syzkaller subsystem for ext2 (as > distinct from ext4)? The syz reproducer seems to know that it should > be mounting using ext2, but also calls it an ext4 file system, which > is a bit weird. I'm guessing there is something specific about the > syzkaller internals which might not make this be practical, but I > thought I should ask. Yeah, having ext2 driver as a separate subsystem makes sense to me since it is completely different codebase. > From the syz reproducer: > > syz_mount_image$ext4(&(0x7f0000000100)='ext2\x00', ...) > > More generally, there are a series of changes that were made to make > ext4 to make it more robust against maliciously fuzzed superblocks, > but we haven't necessarily made sure the same analogous changes have > been made to ext2. I'm not sure how critical this is in practice, > since most distributions don't actually compile fs/ext2 and instead > use CONFIG_EXT4_USE_FOR_EXT2 instead. However, while we maintain ext2 > as a sample "simple" modern file system, I guess we should try to make > sure we do carry those fixes over. > > Jan, as the ext2 maintainer, do you have an opinion? I agree, I try to fix these problems when syzbot finds them. For this one, I've already sent a fix [1] (dropping remains of fragments support from ext2). Honza [1] https://lore.kernel.org/all/20230613103012.22933-1-jack@suse.cz -- Jan Kara SUSE Labs, CR