WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: urmk@xxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Very odd filesystem problem in dom0
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 06 Oct 2004 18:58:03 +0100
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 Oct 2004 19:07:03 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Wed, 06 Oct 2004 11:25:07 EDT." <20041006152507.GA6826@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Just to confirm: you are seeing this problem on 2.6.8.1-xen? I can
reproduce on 2.6 but not on 2.4. Looks like the arguments go into
execve() but get lost sometime during the exec syscall...

 -- Keir

> 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



-------------------------------------------------------
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