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] Btrfs: fix race between block group removal and block group allocation
Date: Wed, 12 Jun 2019 15:23:01 +0200	[thread overview]
Message-ID: <20190612132301.GI3563@twin.jikos.cz> (raw)
In-Reply-To: <20190612100542.1848-1-fdmanana@kernel.org>

On Wed, Jun 12, 2019 at 11:05:42AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>

> Fixes: 04216820fe83d5 ("Btrfs: fix race between fs trimming and block group remove/allocation")
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
> 
> NOTE: this applies only to a 5.2 kernel, although the problem exists in previous
>       kernels starting from 3.19, due to recent changes in the 5.2 merge window
>       that removed the fs_info->pending_chunks, a slightly different version of
>       this patch is needed, one which locks and unlocks the chunk mutex inside
>       the moved block.

Thanks, I'll add it to misc-5.2, the type of the fix qualifies for a
late rc, so I'll send it by the end of the week.


>       Such patch version can be found here:
> 
>       https://www.dropbox.com/s/1sv0hd2xbsn9jrt/Btrfs-fix-race-between-block-group-removal-and-block.patch?dl=0

I'd prefer to get patches instead of links to dropbox. You can send more
patches in a series or as a reply to one of them and put the expected
target version to the subject to eg. like [PATCH for 5.2] or [PATCH for
<= 5.1] and put the note like the above with further details. Thanks.

  reply	other threads:[~2019-06-12 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 10:05 [PATCH] Btrfs: fix race between block group removal and block group allocation fdmanana
2019-06-12 13:23 ` David Sterba [this message]
2019-06-12 13:34   ` Filipe Manana

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=20190612132301.GI3563@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