From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EF91AEB64DD for ; Fri, 21 Jul 2023 23:24:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229656AbjGUXYg (ORCPT ); Fri, 21 Jul 2023 19:24:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57228 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbjGUXYg (ORCPT ); Fri, 21 Jul 2023 19:24:36 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A4D31BE4 for ; Fri, 21 Jul 2023 16:24:35 -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-out1.suse.de (Postfix) with ESMTPS id E82E3218FD; Fri, 21 Jul 2023 23:24:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1689981872; 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=PvX1edvS6cH9/zwsmQIPd0ijr8GUeLi0n7nS+WrHe4I=; b=bV7O1eKFykl6vNStHfgmv6FxS2vIJi2Vrv//tm+RqoFYaH1yeEM+vtof3g/Lli446oipwP E2CJ9zSXOEaryQs3lmJ4HmAJaBeRlQ6M3aiSX8VHxbvxBYSNM+FH/TD+F1hOy5P4Q+Z2Wf oQQlcQksxPBg3PL3Ds+uxNWXAOTlFOw= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1689981872; 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=PvX1edvS6cH9/zwsmQIPd0ijr8GUeLi0n7nS+WrHe4I=; b=AeAfnY89IpZyCrD2fOHSweR4flfvkIV6NP7U8bNiSGYbKkYTxambTrmn4MYZs+5nmZpyaY Aiu01t1RTzH1aGAw== 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 A99A7134BA; Fri, 21 Jul 2023 23:24:32 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Un5yJrATu2QfbwAAMHmgww (envelope-from ); Fri, 21 Jul 2023 23:24:32 +0000 Date: Sat, 22 Jul 2023 01:17:51 +0200 From: David Sterba To: fdmanana@kernel.org Cc: linux-btrfs@vger.kernel.org Subject: Re: [PATCH 0/2] btrfs: fixes for missing error reporting when attaching to a transaction Message-ID: <20230721231751.GG20457@twin.jikos.cz> Reply-To: dsterba@suse.cz References: 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) Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Fri, Jul 21, 2023 at 10:49:19AM +0100, fdmanana@kernel.org wrote: > From: Filipe Manana > > These fix missing error checks and returns when attaching to a transaction > in barrier mode, and waiting for a transaction to commit and finish. These > can make things like an fsync that fallbacks to a transaction commit to > report success to user space when a transaction was aborted and the inode > changes were therefore not persisted. More details on the change logs. > > Filipe Manana (2): > btrfs: check if the transaction was aborted at btrfs_wait_for_commit() > btrfs: check for commit error at btrfs_attach_transaction_barrier() Added to misc-next, thanks.