#273 fsck terminates with buffer overflow detected

bug
open
fsck (38)
5
2009-07-06
2009-07-05
Anonymous
No

Linux ubuntu 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
jfs.fsck versions 1.1.2, 1.1.4, and cvs as of 2009-07-05

Can only mount read only. Kinda sucks being locked out.. I'd take a gamble on a dirty mount option.. I kinda need it for ecryptfs related purposes (lucky for me most of my cruft is backed up)

Using default parameter: -p
The current device is: /dev/mapper/naga-root
Block size in bytes: 4096
Filesystem size in blocks: 37607424
**Phase 0 - Replay Journal Log
logredo failed (rc=-245). fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
**Phase 2 - Count links
Incorrect link counts have been detected. Will correct.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
File system object FF131272 is linked as: /var/lib/mythtv/recordings/1022_20090626182700.mpg
cannot repair the data format error(s) in this file.
cannot repair FF131272. Will release.
File system object DF238023 is linked as: /var/lib/mythtv/recordings
File system object DF663639 is linked as: /home/mark/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWYw1qHSqzWxR-T0bOmVGFBqKLnhbZEpGgESUHav.TrEIpAaNeW3eaA3.---/ECRYPTFS_FNEK_ENCRYPTED.FWYw1qHSqzWxR-T0bOmVGFBqKLnhbZEpGgESjEiQEzZLow1inOVY1v.lmU--/ECRYPTFS_FNEK_ENCRYPTED.FWYw1qHSqzWxR-T0bOmVGFBqKLnhbZEpGgES0XUcUI6z-nJCf0VJbk0kvU--/ECRYPTFS_FNEK_ENCRYPTED.FWYw1qHSqzWxR-T0bOmVGFBqKLnhbZEpGgESaqwt3JiN33HP0BsMOgC3T---/ECRYPTFS_FNEK_ENCRYPTED.FWYw1qHSqzWxR-T0bOmVGFBqKLnhbZEpGgES777ZOa34Qw9WWtkTQAwBcU--/ECRYPTFS_FNEK_ENCRYP
*** buffer overflow detected ***: ./jfs_fsck terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x37)[0x7f8b4bbcd2c7]
/lib/libc.so.6[0x7f8b4bbcb170]
/lib/libc.so.6[0x7f8b4bbca22d]
./jfs_fsck[0x4251f3]
./jfs_fsck[0x410ad8]
./jfs_fsck[0x412d7c]
./jfs_fsck[0x422790]
./jfs_fsck[0x422f8d]
./jfs_fsck[0x424bd0]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7f8b4baec5a6]
./jfs_fsck[0x401c29]
======= Memory map: ========
00400000-00435000 r-xp 00000000 00:11 30226 /usr/src/crap/jfsutils/fsck/jfs_fsck
00634000-00635000 r--p 00034000 00:11 30226 /usr/src/crap/jfsutils/fsck/jfs_fsck
00635000-00663000 rw-p 00035000 00:11 30226 /usr/src/crap/jfsutils/fsck/jfs_fsck
00663000-006fb000 rw-p 00663000 00:00 0
01ba7000-0263a000 rw-p 01ba7000 00:00 0 [heap]
7f8b4b8b6000-7f8b4b8cc000 r-xp 00000000 00:11 1766 /lib/libgcc_s.so.1
7f8b4b8cc000-7f8b4bacc000 ---p 00016000 00:11 1766 /lib/libgcc_s.so.1
7f8b4bacc000-7f8b4bacd000 r--p 00016000 00:11 1766 /lib/libgcc_s.so.1
7f8b4bacd000-7f8b4bace000 rw-p 00017000 00:11 1766 /lib/libgcc_s.so.1
7f8b4bace000-7f8b4bc36000 r-xp 00000000 00:11 33 /lib/libc-2.9.so
7f8b4bc36000-7f8b4be36000 ---p 00168000 00:11 33 /lib/libc-2.9.so
7f8b4be36000-7f8b4be3a000 r--p 00168000 00:11 33 /lib/libc-2.9.so
7f8b4be3a000-7f8b4be3b000 rw-p 0016c000 00:11 33 /lib/libc-2.9.so
7f8b4be3b000-7f8b4be40000 rw-p 7f8b4be3b000 00:00 0
7f8b4be40000-7f8b4be43000 r-xp 00000000 00:11 7286 /lib/libuuid.so.1.2
7f8b4be43000-7f8b4c043000 ---p 00003000 00:11 7286 /lib/libuuid.so.1.2
7f8b4c043000-7f8b4c044000 r--p 00003000 00:11 7286 /lib/libuuid.so.1.2
7f8b4c044000-7f8b4c045000 rw-p 00004000 00:11 7286 /lib/libuuid.so.1.2
7f8b4c045000-7f8b4c065000 r-xp 00000000 00:11 20 /lib/ld-2.9.so
7f8b4c232000-7f8b4c255000 rw-p 7f8b4c232000 00:00 0
7f8b4c25f000-7f8b4c264000 rw-p 7f8b4c25f000 00:00 0
7f8b4c264000-7f8b4c265000 r--p 0001f000 00:11 20 /lib/ld-2.9.so
7f8b4c265000-7f8b4c266000 rw-p 00020000 00:11 20 /lib/ld-2.9.so
7fff54250000-7fff54265000 rw-p 7ffffffea000 00:00 0 [stack]
7fff543fe000-7fff543ff000 r-xp 7fff543fe000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Aborted (core dumped)

Discussion

  • Nobody/Anonymous

    Was looking at the other open segfault bug report, and rebuilt cvs with -g cflags and -static libs, and fsck completed successfully.

    I'm wierded out, but happy I got my root system back online. :-/

     
  • David Kleikamp

    David Kleikamp - 2009-07-06

    Would you still have the binary that corresponds to the output posted in the bug report? Running objdump -t against the binary and sending me the output may help me determine where the buffer overflow occurred.

     
  • David Kleikamp

    David Kleikamp - 2009-07-06
    • assigned_to: nobody --> shaggyk
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks