mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Jeff Layton <jlayton@kernel.org>
Cc: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
	Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [PATCH v4 0/4] btrfs: handle -ENOMEM errors in some synchronous dirops without aborting
Date: Mon, 7 Sep 2026 12:47:32 +0200	[thread overview]
Message-ID: <20260907104732.GS9053@twin.jikos.cz> (raw)
In-Reply-To: <20260825-btrfs-enomem-v4-0-b9363fa8714a@kernel.org>

On Tue, Aug 25, 2026 at 12:04:16PM -0400, Jeff Layton wrote:
> This version is almost exactly the same as v3, but I've dropped the two
> patches that change btrfs_insert_orphan_item() and
> btrfs_del_orphan_item() to use stack allocations. We have no known
> occurrences of those allocations failing, and I'm comfortable not
> solving that problem until we know that it is one.

Thanks.

> Jeff Layton (4):
>       btrfs: split btrfs_insert_delayed_dir_index() into prealloc and commit phases
>       btrfs: pre-allocate delayed dir index before btree modification
>       btrfs: handle ENOMEM from btrfs_insert_dir_item() without aborting
>       btrfs: pre-allocate delayed dir index for non-overwrite rename

Added to for-next.

      parent reply	other threads:[~2026-09-07 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 16:04 Jeff Layton
2026-08-25 16:04 ` [PATCH v4 1/4] btrfs: split btrfs_insert_delayed_dir_index() into prealloc and commit phases Jeff Layton
2026-08-25 16:04 ` [PATCH v4 2/4] btrfs: pre-allocate delayed dir index before btree modification Jeff Layton
2026-08-25 16:04 ` [PATCH v4 3/4] btrfs: handle ENOMEM from btrfs_insert_dir_item() without aborting Jeff Layton
2026-08-25 16:04 ` [PATCH v4 4/4] btrfs: pre-allocate delayed dir index for non-overwrite rename Jeff Layton
2026-09-07 10:47 ` 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=20260907104732.GS9053@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jlayton@kernel.org \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wqu@suse.com \
    /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
all inboxes | Powered by JetHome®