Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
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
Date: Sat, 22 Jul 2023 01:17:51 +0200	[thread overview]
Message-ID: <20230721231751.GG20457@twin.jikos.cz> (raw)
In-Reply-To: <cover.1689932501.git.fdmanana@suse.com>

On Fri, Jul 21, 2023 at 10:49:19AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> 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.

      parent reply	other threads:[~2023-07-21 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  9:49 [PATCH 0/2] btrfs: fixes for missing error reporting when attaching to a transaction fdmanana
2023-07-21  9:49 ` [PATCH 1/2] btrfs: check if the transaction was aborted at btrfs_wait_for_commit() fdmanana
2023-07-21 10:18   ` Qu Wenruo
2023-07-21  9:49 ` [PATCH 2/2] btrfs: check for commit error at btrfs_attach_transaction_barrier() fdmanana
2023-07-21 10:20   ` Qu Wenruo
2023-07-21 23:17 ` David Sterba [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230721231751.GG20457@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox