From: Murlin W. <mw...@no...> - 2010-02-24 23:49:52
Attachments:
swapon03-cleanup-v2.patch
Murlin Wenzel.vcf
|
Added clean_swap() to cleanup routine. This makes sure all leftover swap files are removed. Signed-off-By: Murlin Ray Wenzel mw...@no... Murlin Ray Wenzel Sr. Engineer mw...@no... Office: 801 861 5748 Cell: 801 380 4520 Novell Making IT Work As One. www.novell.com |
From: Garrett C. <yan...@gm...> - 2010-02-25 01:09:10
|
On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: > Added clean_swap() to cleanup routine. This makes sure all leftover swap files are removed. > > Signed-off-By: Murlin Ray Wenzel mw...@no... Committed -- thanks! -Garrett |
From: Rishikesh K R. <ris...@li...> - 2010-02-25 06:26:41
|
On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: > > Added clean_swap() to cleanup routine. This makes sure all leftover swap files are removed. > > > > Signed-off-By: Murlin Ray Wenzel mw...@no... > > Committed -- thanks! > -Garrett Thanks Garret & Murlin. -Rishi > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Ltp-list mailing list > Ltp...@li... > https://lists.sourceforge.net/lists/listinfo/ltp-list -- Thanks & Regards Rishi LTP Maintainer IBM, LTC, Bangalore Please join IRC #ltp @ irc.freenode.net |
From: Rishikesh K R. <ris...@li...> - 2010-03-10 12:16:11
Attachments:
strace-log-swapon03
|
On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: > On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: > > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: > > > Added clean_swap() to cleanup routine. This makes sure all leftover swap files are removed. > > > > > > Signed-off-By: Murlin Ray Wenzel mw...@no... > > > > Committed -- thanks! > > -Garrett > > Thanks Garret & Murlin. Hi Murlin, can you please look into this failure as it still fails on my SLES11 & RHEl5.4 boxes. [root@mx3455a bin]# ./swapon03 swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): Operation not permitted swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted swapon03 1 TFAIL : Failed to setup swaps attached is the strace log. -Rishi -- Thanks & Regards Rishi LTP Maintainer IBM, LTC, Bangalore Please join IRC #ltp @ irc.freenode.net |
From: Murlin W. <mw...@no...> - 2010-03-11 15:48:37
|
>>> On 3/10/2010 at 05:15 AM, in message <201...@li...>, Rishikesh K Rajak <ris...@li...> wrote: > On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: >> On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: >> > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: >> > > Added clean_swap() to cleanup routine. This makes sure all leftover swap > files are removed. >> > > >> > > Signed-off-By: Murlin Ray Wenzel mw...@no... >> > >> > Committed -- thanks! >> > -Garrett >> >> Thanks Garret & Murlin. > > > Hi Murlin, > > can you please look into this failure as it still fails on my SLES11 & > RHEl5.4 > boxes. > > [root@mx3455a bin]# ./swapon03 > swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): > Operation not permitted > swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: > unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted > swapon03 1 TFAIL : Failed to setup swaps > > attached is the strace log. > > -Rishi That's the other part of the problem that I'm not sure what to do with yet. The original test was written entirely based on the assumption that there were always a max of 30 swap files available. With newer kernels (SLE11 RHEL5.4) the kernel can be configured so that the max could be as low as 29 if not 28. The kernel is doing the right thing returning EPERM, but the test needs to be re-worked to deal with new maximum limits/possibilites. Murlin |
From: Garrett C. <yan...@gm...> - 2010-03-13 07:32:45
|
On Thu, Mar 11, 2010 at 7:48 AM, Murlin Wenzel <mw...@no...> wrote: >>>> On 3/10/2010 at 05:15 AM, in message > <201...@li...>, Rishikesh K Rajak > <ris...@li...> wrote: >> On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: >>> On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: >>> > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: >>> > > Added clean_swap() to cleanup routine. This makes sure all leftover swap >> files are removed. >>> > > >>> > > Signed-off-By: Murlin Ray Wenzel mw...@no... >>> > >>> > Committed -- thanks! >>> > -Garrett >>> >>> Thanks Garret & Murlin. >> >> >> Hi Murlin, >> >> can you please look into this failure as it still fails on my SLES11 & >> RHEl5.4 >> boxes. >> >> [root@mx3455a bin]# ./swapon03 >> swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): >> Operation not permitted >> swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: >> unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted >> swapon03 1 TFAIL : Failed to setup swaps >> >> attached is the strace log. > > That's the other part of the problem that I'm not sure what to do with yet. The original test was written entirely based on the assumption that there were always a max of 30 swap files available. With newer kernels (SLE11 RHEL5.4) the kernel can be configured so that the max could be as low as 29 if not 28. The kernel is doing the right thing returning EPERM, but the test needs to be re-worked to deal with new maximum limits/possibilites. It should actually be KERNEL_MAX - (CONFIG_MIGRATION enabled ? 2 : 0) - used_swap_devices ... NOTES The partition or path must be prepared with mkswap(8). There is an upper limit on the number of swap files that may be used, defined by the kernel constant MAX_SWAPFILES. Before kernel 2.4.10, MAX_SWAPFILES has the value 8; since kernel 2.4.10, it has the value 32. Since kernel 2.6.18, the limit is decreased by 2 (thus: 30) if the kernel is built with the CONFIG_MIGRATION option (which reserves two swap table entries for the page migration features of mbind(2) and migrate_pages(2)). The fun unknown is CONFIG_MIGRATION -- how do you know whether or not this is set from userspace? There's too much handwaving in this testcase that needs to be fixed. Thanks, -Garrett |
From: Murlin W. <mw...@no...> - 2010-03-13 17:26:33
Attachments:
Murlin Wenzel.vcf
|
>>> On 3/13/2010 at 12:32 AM, in message <364...@ma...>, Garrett Cooper <yan...@gm...> wrote: > On Thu, Mar 11, 2010 at 7:48 AM, Murlin Wenzel <mw...@no...> wrote: >>>>> On 3/10/2010 at 05:15 AM, in message >> <201...@li...>, Rishikesh K Rajak >> <ris...@li...> wrote: >>> On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: >>>> On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: >>>> > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: >>>> > > Added clean_swap() to cleanup routine. This makes sure all leftover swap >>> files are removed. >>>> > > >>>> > > Signed-off-By: Murlin Ray Wenzel mw...@no... >>>> > >>>> > Committed -- thanks! >>>> > -Garrett >>>> >>>> Thanks Garret & Murlin. >>> >>> >>> Hi Murlin, >>> >>> can you please look into this failure as it still fails on my SLES11 & >>> RHEl5.4 >>> boxes. >>> >>> [root@mx3455a bin]# ./swapon03 >>> swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): >>> Operation not permitted >>> swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: >>> unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted >>> swapon03 1 TFAIL : Failed to setup swaps >>> >>> attached is the strace log. >> >> That's the other part of the problem that I'm not sure what to do with yet. > The original test was written entirely based on the assumption that there > were always a max of 30 swap files available. With newer kernels (SLE11 > RHEL5.4) the kernel can be configured so that the max could be as low as 29 > if not 28. The kernel is doing the right thing returning EPERM, but the test > needs to be re-worked to deal with new maximum limits/possibilites. > > It should actually be KERNEL_MAX - (CONFIG_MIGRATION enabled ? 2 : 0) > - used_swap_devices ... > > NOTES > The partition or path must be prepared with mkswap(8). > > There is an upper limit on the number of swap files that may be > used, > defined by the kernel constant MAX_SWAPFILES. Before kernel > 2.4.10, > MAX_SWAPFILES has the value 8; since kernel 2.4.10, it has the > value > 32. Since kernel 2.6.18, the limit is decreased by 2 (thus: 30) if > the > kernel is built with the CONFIG_MIGRATION option (which reserves > two > swap table entries for the page migration features of mbind(2) > and > migrate_pages(2)). > > The fun unknown is CONFIG_MIGRATION -- how do you know whether or > not this is set from userspace? There's too much handwaving in this > testcase that needs to be fixed. That's my point. There are even more config options in newer kernels which affect the number of swap files. AFAIK none of that info is available to userspace app. The only known is MAX_SWAPFILES which is 32, or 8 on 2.4 kernels. The current test makes an assumption that there would always be 32 or 30 swapfiles available based on a kernel config at some point in the past. I'm thinking the test should just use MAX_SWAPFILES(32 in this case), try to create that many until EPERM error is returned, provide that TINFO to tester, clean up everything and if that succeeds call the test a pass. It is too ugly trying to start guessing about is 29 ok, or 30 ok or 32 ok with no way of knowing how the kernel was configured. -- Murlin Ray Wenzel mw...@no... Office: 801 861 5748 Cell: 801 380 4520 Novell, Making IT work as one. http://www.novell.com |
From: Garrett C. <yan...@gm...> - 2010-03-13 21:56:33
|
On Sat, Mar 13, 2010 at 9:26 AM, Murlin Wenzel <mw...@no...> wrote: >>>> On 3/13/2010 at 12:32 AM, in message > <364...@ma...>, Garrett Cooper > <yan...@gm...> wrote: >> On Thu, Mar 11, 2010 at 7:48 AM, Murlin Wenzel <mw...@no...> wrote: >>>>>> On 3/10/2010 at 05:15 AM, in message >>> <201...@li...>, Rishikesh K Rajak >>> <ris...@li...> wrote: >>>> On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: >>>>> On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: >>>>> > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: >>>>> > > Added clean_swap() to cleanup routine. This makes sure all leftover swap >>>> files are removed. >>>>> > > >>>>> > > Signed-off-By: Murlin Ray Wenzel mw...@no... >>>>> > >>>>> > Committed -- thanks! >>>>> > -Garrett >>>>> >>>>> Thanks Garret & Murlin. >>>> >>>> >>>> Hi Murlin, >>>> >>>> can you please look into this failure as it still fails on my SLES11 & >>>> RHEl5.4 >>>> boxes. >>>> >>>> [root@mx3455a bin]# ./swapon03 >>>> swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): >>>> Operation not permitted >>>> swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: >>>> unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted >>>> swapon03 1 TFAIL : Failed to setup swaps >>>> >>>> attached is the strace log. >>> >>> That's the other part of the problem that I'm not sure what to do with yet. >> The original test was written entirely based on the assumption that there >> were always a max of 30 swap files available. With newer kernels (SLE11 >> RHEL5.4) the kernel can be configured so that the max could be as low as 29 >> if not 28. The kernel is doing the right thing returning EPERM, but the test >> needs to be re-worked to deal with new maximum limits/possibilites. >> >> It should actually be KERNEL_MAX - (CONFIG_MIGRATION enabled ? 2 : 0) >> - used_swap_devices ... >> >> NOTES >> The partition or path must be prepared with mkswap(8). >> >> There is an upper limit on the number of swap files that may be >> used, >> defined by the kernel constant MAX_SWAPFILES. Before kernel >> 2.4.10, >> MAX_SWAPFILES has the value 8; since kernel 2.4.10, it has the >> value >> 32. Since kernel 2.6.18, the limit is decreased by 2 (thus: 30) if >> the >> kernel is built with the CONFIG_MIGRATION option (which reserves >> two >> swap table entries for the page migration features of mbind(2) >> and >> migrate_pages(2)). >> >> The fun unknown is CONFIG_MIGRATION -- how do you know whether or >> not this is set from userspace? There's too much handwaving in this >> testcase that needs to be fixed. > > That's my point. There are even more config options in newer kernels which affect the number of swap files. AFAIK none of that info is available to userspace app. The only known is MAX_SWAPFILES which is 32, or 8 on 2.4 kernels. The current test makes an assumption that there would always be 32 or 30 swapfiles available based on a kernel config at some point in the past. I'm thinking the test should just use MAX_SWAPFILES(32 in this case), try to create that many until EPERM error is returned, provide that TINFO to tester, clean up everything and if that succeeds call the test a pass. It is too ugly trying to start guessing about is 29 ok, or 30 ok or 32 ok with no way of knowing how the kernel was configured. Here's a good question: where is this information stored in the kernel? If we can create an ltp test module to export some of this data [and extend it to other reporting as necessary] via sysfs STRICTLY for testing, it would help determinism a lot. Thanks, -Garrett |
From: Rishikesh K R. <ris...@li...> - 2010-03-31 09:22:36
|
Hi Murlin, Can you please look into this problem again ? It seems you had some discussion with garret to reach to some conclusion about the reported failure. -Rishi On Sat, Mar 13, 2010 at 01:56:25PM -0800, Garrett Cooper wrote: > On Sat, Mar 13, 2010 at 9:26 AM, Murlin Wenzel <mw...@no...> wrote: > >>>> On 3/13/2010 at 12:32 AM, in message > > <364...@ma...>, Garrett Cooper > > <yan...@gm...> wrote: > >> On Thu, Mar 11, 2010 at 7:48 AM, Murlin Wenzel <mw...@no...> wrote: > >>>>>> On 3/10/2010 at 05:15 AM, in message > >>> <201...@li...>, Rishikesh K Rajak > >>> <ris...@li...> wrote: > >>>> On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: > >>>>> On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: > >>>>> > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: > >>>>> > > Added clean_swap() to cleanup routine. This makes sure all leftover swap > >>>> files are removed. > >>>>> > > > >>>>> > > Signed-off-By: Murlin Ray Wenzel mw...@no... > >>>>> > > >>>>> > Committed -- thanks! > >>>>> > -Garrett > >>>>> > >>>>> Thanks Garret & Murlin. > >>>> > >>>> > >>>> Hi Murlin, > >>>> > >>>> can you please look into this failure as it still fails on my SLES11 & > >>>> RHEl5.4 > >>>> boxes. > >>>> > >>>> [root@mx3455a bin]# ./swapon03 > >>>> swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): > >>>> Operation not permitted > >>>> swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: > >>>> unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted > >>>> swapon03 1 TFAIL : Failed to setup swaps > >>>> > >>>> attached is the strace log. > >>> > >>> That's the other part of the problem that I'm not sure what to do with yet. > >> The original test was written entirely based on the assumption that there > >> were always a max of 30 swap files available. With newer kernels (SLE11 > >> RHEL5.4) the kernel can be configured so that the max could be as low as 29 > >> if not 28. The kernel is doing the right thing returning EPERM, but the test > >> needs to be re-worked to deal with new maximum limits/possibilites. > >> > >> It should actually be KERNEL_MAX - (CONFIG_MIGRATION enabled ? 2 : 0) > >> - used_swap_devices ... > >> > >> NOTES > >> The partition or path must be prepared with mkswap(8). > >> > >> There is an upper limit on the number of swap files that may be > >> used, > >> defined by the kernel constant MAX_SWAPFILES. Before kernel > >> 2.4.10, > >> MAX_SWAPFILES has the value 8; since kernel 2.4.10, it has the > >> value > >> 32. Since kernel 2.6.18, the limit is decreased by 2 (thus: 30) if > >> the > >> kernel is built with the CONFIG_MIGRATION option (which reserves > >> two > >> swap table entries for the page migration features of mbind(2) > >> and > >> migrate_pages(2)). > >> > >> The fun unknown is CONFIG_MIGRATION -- how do you know whether or > >> not this is set from userspace? There's too much handwaving in this > >> testcase that needs to be fixed. > > > > That's my point. There are even more config options in newer kernels which affect the number of swap files. AFAIK none of that info is available to userspace app. The only known is MAX_SWAPFILES which is 32, or 8 on 2.4 kernels. The current test makes an assumption that there would always be 32 or 30 swapfiles available based on a kernel config at some point in the past. I'm thinking the test should just use MAX_SWAPFILES(32 in this case), try to create that many until EPERM error is returned, provide that TINFO to tester, clean up everything and if that succeeds call the test a pass. It is too ugly trying to start guessing about is 29 ok, or 30 ok or 32 ok with no way of knowing how the kernel was configured. > > Here's a good question: where is this information stored in the > kernel? If we can create an ltp test module to export some of this > data [and extend it to other reporting as necessary] via sysfs > STRICTLY for testing, it would help determinism a lot. > Thanks, > -Garrett -- Thanks & Regards Rishi LTP Maintainer IBM, LTC, Bangalore Please join IRC #ltp @ irc.freenode.net |
From: Murlin W. <mw...@no...> - 2010-04-01 14:19:40
|
>>> On 3/31/2010 at 03:22 AM, in message <201...@li...>, Rishikesh K Rajak <ris...@li...> wrote: > Hi Murlin, > > Can you please look into this problem again ? It seems you had some > discussion > with garret to reach to some conclusion about the reported failure. > I'm trying to get back to it, but have been swamped with work right now. The inherent problem is the fact that the test is based on a macro used during kernel build/compile time which was hard coded at one point in time. The maximum number of swap files supported can vary based on kernel compile time switches. I really don't think we want to try and build a kernel module or try to build the test assuming kernel headers and complete config are always available. > -Rishi > > On Sat, Mar 13, 2010 at 01:56:25PM -0800, Garrett Cooper wrote: >> On Sat, Mar 13, 2010 at 9:26 AM, Murlin Wenzel <mw...@no...> wrote: >> >>>> On 3/13/2010 at 12:32 AM, in message >> > <364...@ma...>, Garrett Cooper >> > <yan...@gm...> wrote: >> >> On Thu, Mar 11, 2010 at 7:48 AM, Murlin Wenzel <mw...@no...> wrote: >> >>>>>> On 3/10/2010 at 05:15 AM, in message >> >>> <201...@li...>, Rishikesh K Rajak >> >>> <ris...@li...> wrote: >> >>>> On Thu, Feb 25, 2010 at 11:56:15AM +0530, Rishikesh K Rajak wrote: >> >>>>> On Wed, Feb 24, 2010 at 05:08:56PM -0800, Garrett Cooper wrote: >> >>>>> > On Wed, Feb 24, 2010 at 3:49 PM, Murlin Wenzel <mw...@no...> wrote: >> >>>>> > > Added clean_swap() to cleanup routine. This makes sure all leftover swap >> >>>> files are removed. >> >>>>> > > >> >>>>> > > Signed-off-By: Murlin Ray Wenzel mw...@no... >> >>>>> > >> >>>>> > Committed -- thanks! >> >>>>> > -Garrett >> >>>>> >> >>>>> Thanks Garret & Murlin. >> >>>> >> >>>> >> >>>> Hi Murlin, >> >>>> >> >>>> can you please look into this failure as it still fails on my SLES11 & >> >>>> RHEl5.4 >> >>>> boxes. >> >>>> >> >>>> [root@mx3455a bin]# ./swapon03 >> >>>> swapon03 1 TFAIL : Failed swapon for file swapfile29: errno=EPERM(1): >> >>>> Operation not permitted >> >>>> swapon03 0 TWARN : tst_rmdir(): rmobj(/tmp/swasf2sLb) failed: >> >>>> unlink(/tmp/swasf2sLb/swapfile22) failed; errno=1: Operation not permitted >> >>>> swapon03 1 TFAIL : Failed to setup swaps >> >>>> >> >>>> attached is the strace log. >> >>> >> >>> That's the other part of the problem that I'm not sure what to do with yet. >> >> The original test was written entirely based on the assumption that there >> >> were always a max of 30 swap files available. With newer kernels (SLE11 >> >> RHEL5.4) the kernel can be configured so that the max could be as low as 29 >> >> if not 28. The kernel is doing the right thing returning EPERM, but the > test >> >> needs to be re-worked to deal with new maximum limits/possibilites. >> >> >> >> It should actually be KERNEL_MAX - (CONFIG_MIGRATION enabled ? 2 : 0) >> >> - used_swap_devices ... >> >> >> >> NOTES >> >> The partition or path must be prepared with mkswap(8). >> >> >> >> There is an upper limit on the number of swap files that may be >> >> used, >> >> defined by the kernel constant MAX_SWAPFILES. Before kernel >> >> 2.4.10, >> >> MAX_SWAPFILES has the value 8; since kernel 2.4.10, it has the >> >> value >> >> 32. Since kernel 2.6.18, the limit is decreased by 2 (thus: 30) if >> >> the >> >> kernel is built with the CONFIG_MIGRATION option (which reserves >> >> two >> >> swap table entries for the page migration features of mbind(2) >> >> and >> >> migrate_pages(2)). >> >> >> >> The fun unknown is CONFIG_MIGRATION -- how do you know whether or >> >> not this is set from userspace? There's too much handwaving in this >> >> testcase that needs to be fixed. >> > >> > That's my point. There are even more config options in newer kernels which > affect the number of swap files. AFAIK none of that info is available to > userspace app. The only known is MAX_SWAPFILES which is 32, or 8 on 2.4 > kernels. The current test makes an assumption that there would always be 32 > or 30 swapfiles available based on a kernel config at some point in the past. > I'm thinking the test should just use MAX_SWAPFILES(32 in this case), try to > create that many until EPERM error is returned, provide that TINFO to tester, > clean up everything and if that succeeds call the test a pass. It is too > ugly trying to start guessing about is 29 ok, or 30 ok or 32 ok with no way > of knowing how the kernel was configured. >> >> Here's a good question: where is this information stored in the >> kernel? If we can create an ltp test module to export some of this >> data [and extend it to other reporting as necessary] via sysfs >> STRICTLY for testing, it would help determinism a lot. >> Thanks, >> -Garrett |
From: Murlin W. <mw...@no...> - 2010-04-21 18:08:01
|
>>> On 3/31/2010 at 03:22 AM, in message <201...@li...>, Rishikesh K Rajak <ris...@li...> wrote: > Hi Murlin, > > Can you please look into this problem again ? It seems you had some > discussion > with garret to reach to some conclusion about the reported failure. I hope to grab a little time to look at this again. The big problem is the fact that the MAX_SWAPFILES supported by a particular kernel is not an exported variable. It's a compile time macro defined in a kernel header. There is nothing to export. That brings up a question about what constraints LTP should run under. 1. Can I require kernel headers and the current .config file be present on the build or install system that is going to run LTP? 2. Is there a common place to find the correct kernel headers and config file? 3. How hard would it be to use something like autoconf or some other tool to setup the correct define during LTP build? The only other option I see at this point is similar to what the current code does. Start at a given number of swapfiles expected, then start trying to create more one at a time until an error is returned. That's ugly since the starting point is always subject to change. Murlin |