linux-um archives
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Found the problem...
Date: Sun, 9 Oct 2005 17:37:36 -0500	[thread overview]
Message-ID: <200510091737.36983.rob@landley.net> (raw)
In-Reply-To: <200510092106.00389.blaisorblade@yahoo.it>

On Sunday 09 October 2005 14:06, Blaisorblade wrote:
> On Sunday 09 October 2005 07:54, Rob Landley wrote:
> > When attempting to stat a nonexistent file, 2.6.11 returned a consistent
> > value in st_mode (BFFFF73C, every time), and 2.6.13 is returning random
> > crap that varies from invocation to invocation.  Hence the intermittent
> > failure.
> >
> > We _should_ be checking the error return value from lstat64() before
> > looking at S_ISDIR(), and I'll fix it.  Almost certainly, the value in
> > there is random garbage off the stack, and 2.6.13 simply has different
> > random garbage on the stack.
> >
> > So it's not your problem...
>
> Just to be sure: UML _does_ return an error code from lstat64, right? If
> not, complain again please.

Yeah, it does.  UML is ok.  The check was missing in busybox (I checked in a 
fix to -devel last night, I'll clean it up in 1.0.2 when I release that later 
this week).

The fixed version lasted over 1000 iterations of my testcase, whereas the 
previous version usually barfed somewhere in the first couple dozen.  Looks 
good.

Rob

P.S. Apparently, busybox's not checking the return value bug was in there for 
22 months (introduced in revision 8006, Nov 27, 2003, long before the 1.0 
release) without ever causing a problem.  Go figure.  And even now it only 
manifests under uclibc (not glibc), and even _then_ it's highly intermittent.

And you wonder why I'm working on an automated regression test suite in my 
Copious Free Time (tm)?


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-10-09 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09  5:54 [uml-devel] Found the problem Rob Landley
2005-10-09 19:06 ` Blaisorblade
2005-10-09 22:37   ` Rob Landley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200510091737.36983.rob@landley.net \
    --to=rob@landley.net \
    --cc=blaisorblade@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox