Bug 7371 - kernel sometimes oops on umounting a fat USB hard disk (unable to handle kernel NULL pointer dereference)
Summary: kernel sometimes oops on umounting a fat USB hard disk (unable to handle kern...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-06 09:13 CEST by Thierry Vignaud
Modified: 2015-04-18 20:51 CEST (History)
1 user (show)

See Also:
Source RPM: kernel
CVE:
Status comment:

Attachments
kernel oops trace (unable to handle kernel NULL pointer dereference) (2.42 KB, text/plain)
2012-09-06 09:14 CEST, Thierry Vignaud 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Thierry Vignaud 2012-09-06 09:13:49 CEST 
From times to times (every twice month maybe) kernel sometimes oops on umounting a fat USB hard disk with:
VFS: Busy inodes after unmount of sdd6. Self-destruct in 5 seconds.  Have a nice day...
BUG: unable to handle kernel NULL pointer dereference at 00000000000000f8

See attached trace (3.5.3-desktop-2.mga3).

Note that the USB hard disk remains plugged. I only run "umount /run/media/foo/bar"
Comment 1 Thierry Vignaud 2012-09-06 09:14:33 CEST 
Created attachment 2758 [details]
kernel oops trace (unable to handle kernel NULL pointer dereference)
Thierry Vignaud 2012-09-06 09:14:45 CEST

Summary: kernel sometimes oops on umounting a fat USB hard disk => kernel sometimes oops on umounting a fat USB hard disk (unable to handle kernel NULL pointer dereference)

Comment 2 Marja Van Waes 2015-04-18 20:51:48 CEST 
Sorry, but this bug saw no action since over 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.