public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@kernel.org>
To: Anand Jain <anajain.sg@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: fixes for the received subvol ioctl
Date: Sat, 28 Feb 2026 17:49:16 +0000	[thread overview]
Message-ID: <CAL3q7H6g_M3bpaHy+Sbim2KODhYw2LMtjLo6HJy0e1WOtwkf8A@mail.gmail.com> (raw)
In-Reply-To: <6bcde21c-d297-4063-97dd-836b037c92d8@gmail.com>

On Fri, Feb 27, 2026 at 11:27 PM Anand Jain <anajain.sg@gmail.com> wrote:
>
>
>
> > Filipe Manana (3):
> >   btrfs: fix transaction abort on set received ioctl due to item overflow
> >   btrfs: abort transaction on failure to update root in the received subvol ioctl
> >   btrfs: remove unnecessary transaction abort in the received subvol ioctl
>
>
>
> Can this also be considered for LTS kernels?

I forgot to add a Fixes tag, which is:

Fixes: dd5f9615fc5c ("Btrfs: maintain subvolume items in the UUID tree")

This is both for the first and second patches. I'll add it before
pushing to for-next, thanks.

>
> Otherwise, this looks good to me.
>
> Reviewed-by: Anand Jain [asj@kernel.org](mailto:asj@kernel.org)
>
> Anand

      reply	other threads:[~2026-02-28 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  0:11 [PATCH 0/3] btrfs: fixes for the received subvol ioctl fdmanana
2026-02-27  0:11 ` [PATCH 1/3] btrfs: fix transaction abort on set received ioctl due to item overflow fdmanana
2026-02-27  0:11 ` [PATCH 2/3] btrfs: abort transaction on failure to update root in the received subvol ioctl fdmanana
2026-02-27  0:11 ` [PATCH 3/3] btrfs: remove unnecessary transaction abort " fdmanana
2026-02-27 23:27 ` [PATCH 0/3] btrfs: fixes for " Anand Jain
2026-02-28 17:49   ` Filipe Manana [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=CAL3q7H6g_M3bpaHy+Sbim2KODhYw2LMtjLo6HJy0e1WOtwkf8A@mail.gmail.com \
    --to=fdmanana@kernel.org \
    --cc=anajain.sg@gmail.com \
    --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