Bug 127896

Summary: Possible number overflow in YaST2 LVM
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Michael Cocke <cocke>
Component: InstallationAssignee: Martin Vidner <mvidner>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Critical    
Priority: P5 - None CC: jengelh, mlazar
Version: unspecified   
Target Milestone: ---   
Hardware: i586   
OS: SUSE Other   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michael Cocke 2005-10-12 17:45:07 UTC
In SuSE 10.0 boxed final, - in the expert partitioner, try to create a LVM
larger than 1.9 Tb - it doesn't - it wraps around to a negative number and
obviously doesn't create the partition.
Comment 1 Stefan Hundhammer 2005-10-13 09:36:48 UTC
Congratulations for the least meaningful bug subject of the year. 
Comment 2 Thomas Fehr 2005-10-13 09:39:21 UTC
Need y2log files from /var/log/YaST2/y2log
Comment 3 Arvin Schnell 2005-10-20 13:55:38 UTC
The bindings from LibStorage to YCP cannot handle long long ints:
For values greater 0xffffffff the swig_sizeK_get of LvmVgInfo returns
nil and produces this error message in y2log:

[Y2Perl] YPerl.cc(fromPerlScalar):991 Expected integer, got float, SV
with TYPE: PVNV, FLAGS: TEMP NOK POK pIOK pNOK pPOK
[Y2Perl] YPerl.cc(callInner):336 ... when returning from LibStorage::LvmVgInfo::swig_sizeK_get

So not only LVM but all storage containers are affected -> critical for
SLES10.
Comment 4 Martin Vidner 2005-10-20 14:03:25 UTC
Ugh. There's also some discussion in bug 75798.
Comment 5 Martin Vidner 2006-02-01 15:54:05 UTC
Actually two bugs here:
- unsigned integers presented as signed
- not handling long longs.
Both fixed in yast2-perl-bindings-2.13.3.
Comment 6 Thomas Fehr 2006-05-16 09:25:14 UTC
*** Bug 174795 has been marked as a duplicate of this bug. ***
Comment 7 Martin Vidner 2006-06-05 15:57:35 UTC
*** Bug 75798 has been marked as a duplicate of this bug. ***