From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 193431] 512 byte inodes + inline_data + journal_data == segfaults/buserrors in userspace mmap
Date: Mon, 30 Jan 2017 11:11:25 +0000 [thread overview]
Message-ID: <bug-193431-13602-cJhNfVyoEp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-193431-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=193431
Peter Rabbitson <rabbit@rabbit.us> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #3 from Peter Rabbitson <rabbit@rabbit.us> ---
I assure you the problem is real. In my frustration/excitement I did not
properly trim down the testcase, and ignored the obvious change in behavior (
SIGUS -> SIGSEGV ).
Unfortunately I won't have time in the next couple days to properly trim this
down. All I currently have is the tarball of a minimalistic chroot left over
from a failed debian install ( 35MiB
SHA1:18917303621bd99ef8c319107ed0dcd2eb44abe0 ):
https://ipfs.io/ipfs/QmVbjsxH93Wy4Lnx1pThdd1iQ33TpeysoHuwzFb7awef5U/chroot_with_failing_locales_reconfig.tar.xz
The failure is as follows, showcasing a successful run and a failing run right
after ( the 512 inode size was a red herring: 256 fails as well ):
root@Ahasver:~# dd if=/dev/zero of=zeros.img bs=512M count=1
1+0 records in
1+0 records out
536870912 bytes (537 MB) copied, 11.8806 s, 45.2 MB/s
root@Ahasver:~# losetup -f zeros.img
root@Ahasver:~# mke2fs -t ext4 -j -O inline_data /dev/loop0
mke2fs 1.43.3 (04-Sep-2016)
Discarding device blocks: done
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: 027504fd-e49d-42a3-bcd5-4ea3a05af5ed
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
root@Ahasver:~# mount /dev/loop0 /mnt
root@Ahasver:~# cd /mnt
root@Ahasver:/mnt# tar -Jxf ~/chroot_with_failing_locales_reconfig.tar.xz
root@Ahasver:/mnt# cd chroot_with_failing_locales_reconfig/
root@Ahasver:/mnt/chroot_with_failing_locales_reconfig# ./chroot.bash
root@Ahasver:/# dpkg-reconfigure -u locales
Generating locales (this might take a while)...
en_US.ISO-8859-1... done
en_US.UTF-8... done
Generation complete.
root@Ahasver:/# exit
root@Ahasver:/mnt/chroot_with_failing_locales_reconfig# cd
root@Ahasver:~# umount /mnt
root@Ahasver:~# mount -o data=journal /dev/loop0 /mnt
root@Ahasver:~# cd /mnt/chroot_with_failing_locales_reconfig/
root@Ahasver:/mnt/chroot_with_failing_locales_reconfig# ./chroot.bash
root@Ahasver:/# dpkg-reconfigure -u locales
Generating locales (this might take a while)...
en_US.ISO-8859-1...Bus error
done
en_US.UTF-8...Bus error
done
Generation complete.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-30 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 12:38 [Bug 193431] New: 512 byte inodes + inline_data + journal_data == segfaults/buserrors in userspace mmap bugzilla-daemon
2017-01-29 22:21 ` [Bug 193431] " bugzilla-daemon
2017-01-30 2:56 ` bugzilla-daemon
2017-01-30 11:11 ` bugzilla-daemon [this message]
2017-01-30 11:11 ` [Bug 193431] " bugzilla-daemon
2017-01-30 15:58 ` bugzilla-daemon
2017-01-30 16:07 ` bugzilla-daemon
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=bug-193431-13602-cJhNfVyoEp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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).