Your message dated Sun, 27 Jul 2014 23:41:15 +0200
with message-id <[email protected]>
and subject line util-linux v2.25 contains much improved cfdisk (rewrite)
has caused the Debian Bug report #636907,
regarding /sbin/cfdisk: program segfaults in SLcurses_waddnstr when writing 
partition table
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
636907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636907
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: util-linux
Version: 2.17.2-9
File: /sbin/cfdisk
Severity: normal

The cfdisk program in Debian/Squeeze segfaults when i try to write a
new partition table to a RAID disk.  The disk size is 7 809 794 048
kilobytes, and I try to create a LVM (8e) primary partition filling
the entire disk.  The created partition end up being only 1 367 339
929 kilobytes.  When I ask cfdisk to create it, its partition view
show the new partition filling the entire disk.  But when I ask it to
write the partition table, it segfaults.  I run cfdisk with the
nb_NO.UTF-8 locale, and seeing the valgrind report I suspect this
might be related.

Here is the valgrind output from a test run.

==5815== Memcheck, a memory error detector
==5815== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==5815== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for 
copyright info
==5815== Command: cfdisk /dev/sdb
==5815== Parent PID: 26988
==5815==
==5815== Warning: noted but unhandled ioctl 0x1261 with no size/direction hints
==5815==    This could cause spurious value errors to appear.
==5815==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a 
proper wrapper.
==5815== Warning: noted but unhandled ioctl 0x125f with no size/direction hints
==5815==    This could cause spurious value errors to appear.
==5815==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a 
proper wrapper.
==5815== Invalid read of size 8
==5815==    at 0x4EAEE95: ??? (in /lib/libslang.so.2.2.2)
==5815==    by 0x4EAFBD2: SLcurses_waddnstr (in /lib/libslang.so.2.2.2)
==5815==    by 0x4028EA: ??? (in /sbin/cfdisk)
==5815==    by 0x406224: ??? (in /sbin/cfdisk)
==5815==    by 0x407F1C: ??? (in /sbin/cfdisk)
==5815==    by 0x51AEC4C: (below main) (libc-start.c:228)
==5815==  Address 0x2005987200 is not stack'd, malloc'd or (recently) free'd
==5815==
==5815==
==5815== Process terminating with default action of signal 11 (SIGSEGV)
==5815==  Access not within mapped region at address 0x2005987200
==5815==    at 0x4EAEE95: ??? (in /lib/libslang.so.2.2.2)
==5815==    by 0x4EAFBD2: SLcurses_waddnstr (in /lib/libslang.so.2.2.2)
==5815==    by 0x4028EA: ??? (in /sbin/cfdisk)
==5815==    by 0x406224: ??? (in /sbin/cfdisk)
==5815==    by 0x407F1C: ??? (in /sbin/cfdisk)
==5815==    by 0x51AEC4C: (below main) (libc-start.c:228)
==5815==  If you believe this happened as a result of a stack
==5815==  overflow in your program's main thread (unlikely but
==5815==  possible), you can try to increase the size of the
==5815==  main thread stack using the --main-stacksize= flag.
==5815==  The main thread stack size used in this run was 8388608.
==5815==
==5815== HEAP SUMMARY:
==5815==     in use at exit: 128,613 bytes in 91 blocks
==5815==   total heap usage: 643 allocs, 552 frees, 224,056 bytes allocated
==5815==
==5815== LEAK SUMMARY:
==5815==    definitely lost: 0 bytes in 0 blocks
==5815==    indirectly lost: 0 bytes in 0 blocks
==5815==      possibly lost: 0 bytes in 0 blocks
==5815==    still reachable: 128,613 bytes in 91 blocks
==5815==         suppressed: 0 bytes in 0 blocks
==5815== Rerun with --leak-check=full to see details of leaked memory
==5815==
==5815== For counts of detected and suppressed errors, rerun with: -v
==5815== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages util-linux depends on:
ii  debconf [debconf-2.0]   1.5.36.1         Debian configuration management sy
ii  dpkg                    1.15.8.11        Debian package management system
ii  initscripts             2.88dsf-13.1     scripts for initializing and shutt
ii  install-info            4.13a.dfsg.1-6   Manage installed documentation in
ii  libblkid1               2.17.2-9         block device id library
ii  libc6                   2.11.2-10        Embedded GNU C Library: Shared lib
ii  libncurses5             5.7+20100313-5   shared libraries for terminal hand
ii  libselinux1             2.0.96-1         SELinux runtime shared libraries
ii  libslang2               2.2.2-4          The S-Lang programming library - r
ii  libuuid1                2.17.2-9         Universally Unique ID library
ii  lsb-base                3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  tzdata                  2011d-0squeeze1  time zone and daylight-saving time
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools                    3.0.9-1    utilities for making and checking
ii  kbd                           1.15.2-2   Linux console font and keytable ut
ii  util-linux-locales            2.17.2-9   Locales files for util-linux

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.25-1

Hello!

The new util-linux v2.25 contains a completely rewritten cfdisk program
which is now based on the new (lib)fdisk code. This means cfdisk should
now work equally well as the new fdisk and hopefully the reported bug
should be gone.
If you still see the problem you originally reported with the new version
then please do reopen the bug report and provide some additional information
about it.

Regards,
Andreas Henriksson

--- End Message ---

Reply via email to