Bug 141952 - USB mass storage with Korean file names causes kernel to hang
Summary: USB mass storage with Korean file names causes kernel to hang
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-06 11:11 UTC by Nicholas Allen
Modified: 2015-01-04 22:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-10-03 01:06:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nicholas Allen 2004-12-06 11:11:43 UTC
Description of problem:

When I mounted an IRiver mp3 player, which had Korean file names for
some of the files on it, the kernel would  hang when trying to view
those directories that contained files with Korean names. There was no
problem to list directories which had standard ASCII file names
though. Usually the ls command would segfault and then retrying would
cause the kernel to hang. It was then not possible to unmount the
IRiver player and the only option was to reboot the computer.


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


How reproducible:

Every time

Steps to Reproduce:
1.Plug in IRiber (possibly any USB mass storage device) that contains
Korean characters in the file names.
2.Try to browse a directory containing the file
3.Watch as kernel crashes or hangs with only option to reboot
  
Actual results:


Expected results:


Additional info:

Comment 1 Dave Jones 2005-07-15 18:50:50 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 2 Dave Jones 2005-10-03 01:06:32 UTC
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.

There are a large number of inactive bugs in the database, and this is the only
way to purge them.

Thank you.


Note You need to log in before you can comment on or make changes to this bug.