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 02:56:18 +0000 [thread overview]
Message-ID: <bug-193431-13602-0xyb0PYya5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-193431-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=193431
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tytso@mit.edu
Resolution|--- |INVALID
--- Comment #2 from Theodore Tso <tytso@mit.edu> ---
Using a stock ext4 file system ---- or an xfs file system --- results in the
same segfault in localdef.
So I think Christian is right. This has nothing to do with ext4.
P.S. I just tried with btrfs, and surprise! localdef is also crashing with a
segfault.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-30 3:04 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 [this message]
2017-01-30 11:11 ` bugzilla-daemon
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-0xyb0PYya5@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).