All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: fix a regression with concurrent DIO writes and fsync on the same fd
Date: Tue, 3 Sep 2024 11:50:43 -0400	[thread overview]
Message-ID: <20240903155043.GA3354361@perftesting> (raw)
In-Reply-To: <cover.1724972506.git.fdmanana@suse.com>

On Fri, Aug 30, 2024 at 12:09:35AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Fix a recent regression when doing concurrent direct IO writes and fsync
> using the same fd from multiple threads. This was reported recently by a
> couple users when using QEMU, as well as syzbot. The fix is the first
> patch in the series, the second one is just an improvement for some
> assertions. Details in the change logs of each patch.
> 
> Filipe Manana (2):
>   btrfs: fix race between direct IO write and fsync when using same fd
>   btrfs: add and use helper to verify the calling task has locked the inode
> 

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

      parent reply	other threads:[~2024-09-03 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 23:09 [PATCH 0/2] btrfs: fix a regression with concurrent DIO writes and fsync on the same fd fdmanana
2024-08-29 23:09 ` [PATCH 1/2] btrfs: fix race between direct IO write and fsync when using " fdmanana
2024-09-02 21:38   ` David Sterba
2024-08-29 23:09 ` [PATCH 2/2] btrfs: add and use helper to verify the calling task has locked the inode fdmanana
2024-09-03 15:50 ` Josef Bacik [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=20240903155043.GA3354361@perftesting \
    --to=josef@toxicpanda.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.