From: Josh Triplett <josh@joshtriplett.org>
To: linux-ext4@vger.kernel.org
Cc: 971014@bugs.debian.org
Subject: Reproducible bug in inline_data handling with ACL
Date: Sat, 26 Sep 2020 03:25:12 -0700 [thread overview]
Message-ID: <20200926102512.GA11386@localhost> (raw)
In-Reply-To: <160110861360.7199.11561753808099731033.reportbug@s>
Adding CC to linux-ext4@.
On Sat, Sep 26, 2020 at 01:23:33AM -0700, Josh Triplett wrote:
> In the course of creating some filesystems containing Debian
> installations using `mke2fs -d`, I managed to find a bug in the
> `inline_data` handling, which seems to apply to files containing ACLs.
> On a default Debian installation, /var/log/journal triggered this
> problem.
>
> I managed to create a minimal test case. To reproduce:
>
> mkdir -p target/testdir
> setfacl --restore=- <<EOF
> # file: target/testdir/
> user::rwx
> group::r-x
> group:adm:r-x
> mask::r-x
> other::r-x
> default:user::rwx
> default:group::r-x
> default:group:adm:r-x
> default:mask::r-x
> default:other::r-x
> EOF
> mke2fs -b 4096 -I 256 -O sparse_super2,inline_data,^has_journal -d target disk.img 8M
>
> and then run:
>
> e2fsck -n -f disk.img
>
> This will show:
>
> e2fsck 1.46-WIP (03-Oct-2019)
> Pass 1: Checking inodes, blocks, and sizes
> Inode 12 has INLINE_DATA_FL flag but extended attribute not found. Truncate? no
>
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
>
> disk.img: ********** WARNING: Filesystem still has errors **********
>
> disk.img: 12/2048 files (0.0% non-contiguous), 137/2048 blocks
>
>
> And the kernel ext4 implementation will fail to handle that inode, with
> a message like this:
>
> EXT4-fs error (device loop0): __ext4_iget:4776: inode #3215: block 56: comm ls: invalid block
>
>
> The size of 8M doesn't matter; the issue reproduces with other sizes.
> /etc/mke2fs.conf is unchanged from the defaults. `tune2fs -l disk.img`
> shows the following:
>
> tune2fs 1.46-WIP (03-Oct-2019)
> Filesystem volume name: <none>
> Last mounted on: <not available>
> Filesystem UUID: 931e3151-83db-4c33-be5f-655c9323fab4
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: ext_attr resize_inode dir_index sparse_super2 filetype inline_data sparse_super large_file
> Filesystem flags: signed_directory_hash
> Default mount options: user_xattr acl
> Filesystem state: clean
> Errors behavior: Continue
> Filesystem OS type: Linux
> Inode count: 2048
> Block count: 2048
> Reserved block count: 102
> Free blocks: 1911
> Free inodes: 2036
> First block: 0
> Block size: 4096
> Fragment size: 4096
> Blocks per group: 32768
> Fragments per group: 32768
> Inodes per group: 2048
> Inode blocks per group: 128
> Filesystem created: Sat Sep 26 00:50:53 2020
> Last mount time: n/a
> Last write time: Sat Sep 26 00:50:53 2020
> Mount count: 0
> Maximum mount count: -1
> Last checked: Sat Sep 26 00:50:53 2020
> Check interval: 0 (<none>)
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> First inode: 11
> Inode size: 256
> Required extra isize: 32
> Desired extra isize: 32
> Default directory hash: half_md4
> Directory Hash Seed: df46d104-ed26-4cea-ac61-0feff2a54622
parent reply other threads:[~2020-09-26 10:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <160110861360.7199.11561753808099731033.reportbug@s>]
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=20200926102512.GA11386@localhost \
--to=josh@joshtriplett.org \
--cc=971014@bugs.debian.org \
--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 NNTP newsgroup(s).