Re: [Xen-devel] Very odd filesystem problem in dom0

[urmk@xxxxxxxxxxxxxxxxx]

OK, this is definitely related to the length of the exec string, and the exec
getting corrupted.  I can't recreate it with the obvious echo `perl print 
'a'x100`,
but I can create it with the length of filenames in the directory -- i've even 
gotten it to corrupt to the point that argv[0] is showing up later in the arg
string:

"""
root@durandal:~/temp# ls *
: : No such file or directory
: : No such file or directory
: : No such file or directory
/bin/ls*
2222222222
3333333333
4444444444
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa0
....
"""

/bin/ls was obviously not in that directory.

I'll keep working on narrowing it down more and looking at the kernel code.

-m

On Wed, Oct 06, 2004 at 10:49:42AM -0400, urmk@xxxxxxxxxxxxxxxxx wrote:
> Ah-hah.  It was just sugested to me that the size of the directory might 
> matter:
> It's not quite the number of files, it's the lengh of the argument character
> string.  (Sorry, writing this email stream-of-thought as I test different
> thing)
> 
> Filling a test directory with 100 files (for x in `seq 0 100`; do touch $x; 
> done)
> doesn't trigger it, but filling a test dir with 100 files with long names
> (touch aaaaaaaaaaaaaaaaaaaaaa-$x) does.
> 
> Is xeno changing the size of the exec string buffer in the kernel?


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel