Linux-ext4 Archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: <linux-ext4@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 0/3] e2fsck: expand checking of EA inode
Date: Mon,  6 May 2024 19:41:16 +0200	[thread overview]
Message-ID: <20240506173704.24995-1-jack@suse.cz> (raw)

Hello,

customer has reported that his filesystem was reporting errors from
ext4_iget() about inode with EA_INODE_FL but e2fsck was considering the
filesystem as clean. Indeed the EA inode checking in e2fsck is weak and
lets through several cases of corruption related to EA inodes. This series
adds more strict checking of EA inodes and adds e2fsck tests for them.

								Honza

             reply	other threads:[~2024-05-06 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 17:41 Jan Kara [this message]
2024-05-06 17:41 ` [PATCH 1/3] e2fsck: add more checks for ea inode consistency Jan Kara
2024-05-06 17:41 ` [PATCH 2/3] e2fsck: add tests for EA inodes Jan Kara
2024-05-06 17:41 ` [PATCH 3/3] e2fsck: fix golden output of several tests Jan Kara
2024-05-09 15:01 ` [PATCH 0/3] e2fsck: expand checking of EA inode Theodore Ts'o

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=20240506173704.24995-1-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).