All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs: a couple bug fixes for log replay
Date: Tue,  3 Jun 2025 22:19:56 +0100	[thread overview]
Message-ID: <cover.1748985387.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

Fix invalid inode pointer dereferences in error paths of log replay
and stop ignoring invalid extent types.

V2: Updated patch 1/2 to avoid NULL pointer dereference for the case
    where we find an unexpected/invalid extent type and added RB tag.
    Added patch 2/2.

Filipe Manana (2):
  btrfs: fix invalid inode pointer dereferences during log replay
  btrfs: don't silently ignore unexpected extent type when replaying log

 fs/btrfs/tree-log.c | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-06-03 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 21:19 fdmanana [this message]
2025-06-03 21:19 ` [PATCH v2 1/2] btrfs: fix invalid inode pointer dereferences during log replay fdmanana
2025-06-03 21:19 ` [PATCH v2 2/2] btrfs: don't silently ignore unexpected extent type when replaying log fdmanana
2025-06-03 22:22   ` Boris Burkov
2025-06-04 12:24   ` David Sterba

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=cover.1748985387.git.fdmanana@suse.com \
    --to=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 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.