All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>,
	Naohiro Aota <Naohiro.Aota@wdc.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	David Sterba <dsterba@suse.com>
Subject: Re: [PATCH 0/3] btrfs: zoned: fix zoned extent allocator
Date: Wed, 29 Dec 2021 00:22:31 +0000	[thread overview]
Message-ID: <20211229002230.6qvi5jelmitwjvlz@shindev> (raw)
In-Reply-To: <20211208161814.GL28560@twin.jikos.cz>

On Dec 08, 2021 / 17:18, David Sterba wrote:
> On Wed, Dec 08, 2021 at 12:35:46AM +0900, Naohiro Aota wrote:
> > There are several reports of hung_task on btrfs recently.
> > 
> > - https://github.com/naota/linux/issues/59
> > - https://lore.kernel.org/linux-btrfs/CAJCQCtR=jztS3P34U_iUNoBodExHcud44OQ8oe4Jn3TK=1yFNw@mail.gmail.com/T/

(snip)

> > While we are debugging this issue, we found some faulty behaviors on
> > the zoned extent allocator. It is not the root cause of the hung as we
> > see a similar report also on a regular btrfs. But, it looks like that
> > early -ENOSPC is, at least, making the hung to happen often.
> > 
> > So, this series fixes the faulty behaviors of the zoned extent
> > allocator.
> > 
> > Patch 1 fixes a case when allocation fails in a dedicated block group.
> > 
> > Patches 2 and 3 fix the chunk allocation condition for zoned
> > allocator, so that it won't block a possible chunk allocation.
> > 
> > Naohiro Aota (3):
> >   btrfs: zoned: unset dedicated block group on allocation failure
> >   btrfs: add extent allocator hook to decide to allocate chunk or not
> >   btrfs: zoned: fix chunk allocation condition for zoned allocator
> 
> All seem to be relevant for 5.16-rc so I'll add them to misc-next now to
> give it some testing, pull request next week. Thanks.

Hello David, thanks for your maintainer-ship always.

When I run my test set for zoned btrfs configuration, I keep on observing the
issue that Naohiro addressed with the three patches. The patches are not yet
merged to 5.16-rc7. Can I expect they get merged to rc8?

-- 
Best Regards,
Shin'ichiro Kawasaki

  reply	other threads:[~2021-12-29  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 15:35 [PATCH 0/3] btrfs: zoned: fix zoned extent allocator Naohiro Aota
2021-12-07 15:35 ` [PATCH 1/3] btrfs: zoned: unset dedicated block group on allocation failure Naohiro Aota
2021-12-07 15:35 ` [PATCH 2/3] btrfs: add extent allocator hook to decide to allocate chunk or not Naohiro Aota
2021-12-07 15:35 ` [PATCH 3/3] btrfs: zoned: fix chunk allocation condition for zoned allocator Naohiro Aota
2021-12-08 16:18 ` [PATCH 0/3] btrfs: zoned: fix zoned extent allocator David Sterba
2021-12-29  0:22   ` Shinichiro Kawasaki [this message]
2022-01-03 19:13     ` David Sterba
2022-01-05  2:00       ` Shinichiro Kawasaki

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=20211229002230.6qvi5jelmitwjvlz@shindev \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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.