All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: David Sterba <dsterba@suse.com>,
	torvalds@linux-foundation.org, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs fixes for 6.11-rc6
Date: Wed, 28 Aug 2024 14:18:36 +0200	[thread overview]
Message-ID: <20240828121836.GG25962@suse.cz> (raw)
In-Reply-To: <CAL3q7H5L9ebGLyPkVFOtG7sEfAj7f17e6uzH2g7s5MUc59FAsQ@mail.gmail.com>

On Wed, Aug 28, 2024 at 12:50:22PM +0100, Filipe Manana wrote:
> On Wed, Aug 28, 2024 at 12:23 PM David Sterba <dsterba@suse.com> wrote:
> >
> > Hi,
> >
> > a few more misc fixes. Please pull, thanks.
> >
> > - fix use-after-free when submitting bios for read, after an error and
> >   partially submitted bio the original one is freed while it can be still be
> >   accessed again
> >
> > - fix fstests case btrfs/301, with enabled quotas wait for delayed iputs when
> >   flushing delalloc
> >
> > - fix regression in periodic block group reclaim, an unitialized value can be
> >   returned if there are no block groups to reclaim
> 
> There's some confusion here.
> 
> First, it's not a regression because the uninitialized return value
> has been there since periodic block group reclaim was introduced.

I used the word regression because it's been added in the same
development cycle, i.e. the dynamic reclaim, but yeah maybe it's too
strong.

> Secondly, and more important, is that it doesn't cause any problem
> because the only caller of the function ignores its return value.
> 
> So this is effectively more of a cleanup than anything else, and could
> have waited for the next merge window.
> I see you also added a Fixes tag to the changelog, which will trigger
> stable backports.

For completeness of the periodic reclaim code I'd rather add it now,
before 6.11 is released. The Fixes tag is for reference where it was
added,

> Unless there are compiler versions or static analysis tools that
> complain with warnings, it will be just overhead to backport to stable
> releases.

No backports should be triggered by that because it hasn't been
released

$ git describe --contains e4ca3932ae90
v6.11-rc1~157^2~32

  reply	other threads:[~2024-08-28 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 11:23 [GIT PULL] Btrfs fixes for 6.11-rc6 David Sterba
2024-08-28 11:50 ` Filipe Manana
2024-08-28 12:18   ` David Sterba [this message]
2024-08-28 19:11 ` pr-tracker-bot

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=20240828121836.GG25962@suse.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.