Bug 292481 - SIGSEGV in kpartx when used with relatice device paths
SIGSEGV in kpartx when used with relatice device paths
Product: Fedora
Classification: Fedora
Component: device-mapper-multipath (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Ben Marzinski
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-16 11:12 EDT by Kostas Georgiou
Modified: 2009-01-09 02:15 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 02:15:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kostas Georgiou 2007-09-16 11:12:06 EDT
It looks like find_devname_offset() expects a device path with '/' in it
otherwise it returns a "random" offset.

# gdb kpartx
(gdb) run -l rootvg-letovol
Starting program: /sbin/kpartx -l rootvg-foovol

Program received signal SIGSEGV, Segmentation fault.
0x000000393b677160 in strlen () from /lib64/libc.so.6
(gdb) where
#0  0x000000393b677160 in strlen () from /lib64/libc.so.6
#1  0x000000393b6460bb in vfprintf () from /lib64/libc.so.6
#2  0x000000393b64bf0a in printf () from /lib64/libc.so.6
#3  0x00000000004026cd in main (argc=3, argv=0x7fffb12ebb98) at kpartx.c:368
#4  0x000000393b61dab4 in __libc_start_main () from /lib64/libc.so.6
#5  0x0000000000401659 in _start ()
(gdb) up
#1  0x000000393b6460bb in vfprintf () from /lib64/libc.so.6
(gdb) up
#2  0x000000393b64bf0a in printf () from /lib64/libc.so.6
(gdb) up
#3  0x00000000004026cd in main (argc=3, argv=0x7fffb12ebb98) at kpartx.c:368
368                                     printf("%s%s%d : 0 %" PRIu64 " %s %"
(gdb) print off
$1 = 1322333445
(gdb) print device+off
$2 = 0x800000000001 <Address 0x800000000001 out of bounds>
Comment 1 Kostas Georgiou 2008-04-16 10:55:40 EDT
still there in f8, you need a cd /dev/mapper; kpartx -l someexistingdev to fail
Comment 2 Bug Zapper 2008-11-26 02:48:44 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-01-09 02:15:56 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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