All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: fix a couple races between fsync and other code
Date: Mon, 8 Mar 2021 19:06:05 +0100	[thread overview]
Message-ID: <20210308180605.GF7604@twin.jikos.cz> (raw)
In-Reply-To: <20210304174418.GV7604@twin.jikos.cz>

On Thu, Mar 04, 2021 at 06:44:19PM +0100, David Sterba wrote:
> On Tue, Feb 23, 2021 at 12:08:46PM +0000, fdmanana@kernel.org wrote:
> > From: Filipe Manana <fdmanana@suse.com>
> > 
> > The first patch fixes a race between fsync and memory mapped writes, which
> > can result in corruptions. The second one fixes a different race that in
> > practice should be "impossible" to happen, but in case it's triggered
> > somehow, results in not logging an inode when it has new extents. The last
> > patch just removes some no longer needed code.
> > 
> > The first patch, as mentioned in its changelog, depends on Josef's patchset
> > which has the subject:
> > 
> >    "Introduce a mmap sem to deal with some mmap issues"
> 
> The patchset is now in for-next so I'll add your fixes on top of that.

Moved to misc-next, thanks.

      reply	other threads:[~2021-03-08 18:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 12:08 [PATCH 0/3] btrfs: fix a couple races between fsync and other code fdmanana
2021-02-23 12:08 ` [PATCH 1/3] btrfs: fix race between memory mapped writes and fsync fdmanana
2021-02-23 12:08 ` [PATCH 2/3] btrfs: fix race between marking inode needs to be logged and log syncing fdmanana
2021-02-23 12:08 ` [PATCH 3/3] btrfs: remove stale comment and logic from btrfs_inode_in_log() fdmanana
2021-03-04 17:44 ` [PATCH 0/3] btrfs: fix a couple races between fsync and other code David Sterba
2021-03-08 18:06   ` 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=20210308180605.GF7604@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 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.