[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <bug-12375-13602@http.bugzilla.kernel.org/>
Date: Wed, 7 Jan 2009 02:56:33 -0800 (PST)
From: bugme-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 12375] New: ext4_block_to_path block too big cause cpu to burn
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@...nel-bugs.osdl.org
ReportedBy: dmaciejak@...tinet.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists