Bug 130189

Summary: kernel 2.6.7-1.494.2.2 oopses when accessing FAT partition
Product: [Fedora] Fedora Reporter: Pavel Rosenboim <pavel1r>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 2CC: hardawayd, pavel.rosenboim, pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-29 05:51:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Kernel messages none

Description Pavel Rosenboim 2004-08-17 20:11:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040803

Description of problem:
I have a FAT32 partition (from Win98Se) with few directories whose
name displayed as gibberish (they are probably in Russian). whenever I
try to access these directories, kernel oopses. Windows scandisk does
not report any errors. This only started to happen in latest kernel
2.6.7-1.494.2.2. I renamed these directories to sane names, so I
probably won't be able to reproduce the bug now.

Version-Release number of selected component (if applicable):
kernel-2.6.7-1.494.2.2

How reproducible:
Always

Steps to Reproduce:
1. See description.
2.
3.
    

Actual Results:  kernel oops

Expected Results:  access directory

Additional info:

Comment 1 Pavel Rosenboim 2004-08-17 20:12:59 UTC
Created attachment 102809 [details]
Kernel messages

kernel messages I got trying to ls the directory

Comment 2 Don Hardaway 2004-09-04 18:25:02 UTC
I am having the same problem.

Comment 3 Dave Jones 2004-11-27 22:35:09 UTC
mass update for old bugs:

Is this still a problem in the 2.6.9 based kernel update ?


Comment 4 Pavel R 2004-11-28 07:38:23 UTC
I changed name of the directory to more sane and never saw that problem since.