From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12375] New: ext4_block_to_path block too big cause cpu to burn
Date: Wed, 7 Jan 2009 02:56:33 -0800 (PST) [thread overview]
Message-ID: <bug-12375-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12375
Summary: ext4_block_to_path block too big cause cpu to burn
Product: File System
Version: 2.5
KernelVersion: 2.6.28
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: dmaciejak@fortinet.com
Latest working kernel version: none
Earliest failing kernel version: unknow
Distribution: ubuntu
Hardware Environment: dell optiplex 740
Software Environment:
Problem Description:
when mounting specially crafted ext4 image, after some few seconds (5s),
kern.log is filled with some data and cpu reaches 100%
Steps to reproduce:
bunzip the image file enclosed and mount the image with mount -t ext4 -o loop
ext4.img /media/tmp
note: i also tried the 2.6.28-ext4-3 patch but it does not help
Regards,
David Maciejak
Fortinet's FortiGuard Global Security Research Team
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-01-07 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 10:56 bugme-daemon [this message]
2009-01-07 10:57 ` [Bug 12375] ext4_block_to_path block too big cause cpu to burn bugme-daemon
2009-01-07 10:57 ` bugme-daemon
2009-01-17 23:44 ` bugme-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-12375-13602@http.bugzilla.kernel.org/ \
--to=bugme-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 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.