From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 124D52CA6 for ; Tue, 14 Mar 2023 22:05:41 +0000 (UTC) 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-out1.suse.de (Postfix) with ESMTPS id 2641221B54; Tue, 14 Mar 2023 22:05:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1678831540; h=from:from:reply-to: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=ElR8pKBKL+7F7ATiZZYZBbN4l0PaI0eoqh0mNGebGjw=; b=ASFqSZIwk/+YExWlI6/vuywNTBqWbY8IMP3fMTOBFiswATT4JPykvwCN0np9Q6xsEYKR0g EuyF6iDcKyBuYjKgWBifW144p9MhvhTOWL+bG97NTF+v0aLRLNG/zXGhNeYqgnM21k1PfA Zsjpe5U6Y63ok/jmGbCBWKQWiWQtQE8= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1678831540; h=from:from:reply-to: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=ElR8pKBKL+7F7ATiZZYZBbN4l0PaI0eoqh0mNGebGjw=; b=Ya6Kb/2UgdZ7CMRMZeP920p8RfK3yekE1yRjyb1hk/qoP8RIZJcek1jHx6k4hAMvxvv0bS harIhHlu6bF/5bCg== 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 EF47F13A1B; Tue, 14 Mar 2023 22:05:39 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id eZpnObPvEGSqCgAAMHmgww (envelope-from ); Tue, 14 Mar 2023 22:05:39 +0000 Date: Tue, 14 Mar 2023 22:59:33 +0100 From: David Sterba To: Linux regressions mailing list Cc: Josef Bacik , linux-btrfs@vger.kernel.org, kernel-team@fb.com, Guenter Roeck Subject: Re: [PATCH 8/8] btrfs: turn on -Wmaybe-uninitialized Message-ID: <20230314215933.GT10580@suse.cz> Reply-To: dsterba@suse.cz References: <1d9deaa274c13665eca60dee0ccbc4b56b506d06.1671221596.git.josef@toxicpanda.com> <20230222025918.GA1651385@roeck-us.net> <20230222163855.GU10580@twin.jikos.cz> <6c308ddc-60f8-1b4d-28da-898286ddb48d@roeck-us.net> Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) On Sun, Mar 12, 2023 at 02:06:40PM +0100, Linux regression tracking (Thorsten Leemhuis) wrote: > On 22.02.23 18:18, Guenter Roeck wrote: > > On 2/22/23 08:38, David Sterba wrote: > >> On Tue, Feb 21, 2023 at 06:59:18PM -0800, Guenter Roeck wrote: > >>> On Fri, Dec 16, 2022 at 03:15:58PM -0500, Josef Bacik wrote: > This discussion seems to have stalled, but from a kernelci report it > looks like above warning still happens: > https://lore.kernel.org/all/640bceb7.a70a0220.af8cd.146b@mx.google.com/ > > @btrfs developers, do you still have it on your radar? I'm aware of the warnings and that it's caused by enabling the -Wmaybe-uninitialized warning. One has a patch, IIRC there are 2-3 more, so either there's a fix or the commit enabling the warning will be reverted before 6.3 final.