Bug 551468

Summary: [abrt] crash detected in dosfstools-3.0.1-6.fc12
Product: [Fedora] Fedora Reporter: Kazimieras Vaina <kazimieras.vaina>
Component: dosfstoolsAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bernie+fedora, jskarvad, kasal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:876d9c249af0775641d42851c5ae2c34cd70cccf
Fixed In Version: dosfstools-3.0.9-2.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-14 01:34:34 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
File: backtrace none

Description Kazimieras Vaina 2009-12-30 21:28:11 UTC 
abrt 1.0.0 detected a crash.

How to reproduce
-----
1.First i run: fsck.vfat /dev/sdb1
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  71:42/20, 72:4f/20, 73:4f/20, 74:54/20
1) Copy original to backup
2) Copy backup to original
3) No action
? 1
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 1
Orphaned long file name part "gx.dll"
1: Delete.
2: Leave it.
? 1
Reclaimed 385 unused clusters (1576960 bytes).
Free cluster summary wrong (394383 vs. really 394768)
1) Correct
2) Don't correct
? 1
Leaving file system unchanged.
/dev/sdb1: 356 files, 100260/495028 clusters

2. The I run: fsck.vfat -a /dev/sdb1 or fsck.vfat -y /dev/sdb1 and the error occurs.

Comment
-----
I tried to fix FAT file system eerors. The fsck.vfat -a /dev/sdb1 or fsck.vfat -y /dev/sdb1 resulted in errors, but fsck.vfat -w -r /dev/sdb1 did work after ansvering a fiew questions.
It seems that interactive mode works but batch mode doesn't.

backtrace
-----
Debuginfo absent: 0e779f0ad79e5478e077924603db4267836373eb
Debuginfo absent: 37f924e346314480e4cd5171909920530ee5f8ca
Debuginfo absent: 68354843e5200f56efe06888e9c389ee1e43aca2
Debuginfo absent: 749468ee016157e0d06e5f7a4f369a444ef06205
Debuginfo absent: 9feb0c25009cf269edc39e1712fc28b8fc71e4ba
Debuginfo absent: a17abc9143f461a7bc63a1e0d1d0ae3554d3c473
Debuginfo absent: a4fe82f4cad4d0888438fa37b692f6d590f1a2c7
Debuginfo absent: a8a2e267e911671383d5b0f26f0ae1fa3fc53ecc
Debuginfo absent: c033d23c920ea60ae44fd0cd660b37aaa44cb938
Debuginfo absent: db35e1ccd57ac6bd99dcfc37b1e86a48849be03c
Core was generated by `fsck.vfat -a /dev/sdb1'.
Program terminated with signal 6, Aborted.
#0  0x00d98416 in __kernel_vsyscall ()

Thread 1 (Thread 23250):
#0  0x00d98416 in __kernel_vsyscall ()
No symbol table info available.
#1  0x006c5a81 in raise () from /lib/libc.so.6
No symbol table info available.
#2  0x006c734a in abort () from /lib/libc.so.6
No symbol table info available.
#3  0x00702e5d in __libc_message () from /lib/libc.so.6
No symbol table info available.
#4  0x0078ec5d in __fortify_fail () from /lib/libc.so.6
No symbol table info available.
#5  0x0078cd7a in __chk_fail () from /lib/libc.so.6
No symbol table info available.
#6  0x0078c4a8 in _IO_str_chk_overflow () from /lib/libc.so.6
No symbol table info available.
#7  0x007076e6 in _IO_default_xsputn_internal () from /lib/libc.so.6
No symbol table info available.
#8  0x006db1f7 in vfprintf () from /lib/libc.so.6
No symbol table info available.
#9  0x0078c557 in __vsprintf_chk () from /lib/libc.so.6
No symbol table info available.
#10 0x0078c49d in __sprintf_chk () from /lib/libc.so.6
No symbol table info available.
#11 0x0804d223 in exit ()
No symbol table info available.
#12 0x0804e0b0 in exit ()
No symbol table info available.
#13 0x0804907f in exit ()
No symbol table info available.
#14 0x006b1bb6 in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
#15 0x08048b01 in exit ()
No symbol table info available.

cmdline: fsck.vfat -a /dev/sdb1
component: dosfstools
executable: /sbin/dosfsck
kernel: 2.6.31.9-174.fc12.i686.PAE
package: dosfstools-3.0.1-6.fc12
rating: 3
reason: Process was terminated by signal 6
Comment 1 Kazimieras Vaina 2009-12-30 21:28:14 UTC 
Created attachment 381007 [details]
File: backtrace
Comment 2 Bernie Innocenti 2010-02-01 20:13:50 UTC 
The -a flag triggers memory corruption in dosfsck 3.0.1.

dosfsck 3.0.3 (in karmic) and 3.0.6 (in rawhide) are free of this bug. Please, push one of these versions as an update to F-12.
Comment 3 Fedora Update System 2010-03-16 14:46:54 UTC 
dosfstools-3.0.9-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/dosfstools-3.0.9-2.fc12
Comment 4 Jaroslav Škarvada 2010-03-16 14:49:26 UTC 
dosfstools-3.0.9-2.fc12 pushed into testing.
Comment 5 Fedora Update System 2010-03-18 03:25:29 UTC 
dosfstools-3.0.9-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update dosfstools'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/dosfstools-3.0.9-2.fc12
Comment 6 Fedora Update System 2010-04-14 01:34:28 UTC 
dosfstools-3.0.9-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.