From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Found the problem...
Date: Sun, 9 Oct 2005 00:54:05 -0500 [thread overview]
Message-ID: <200510090054.07750.rob@landley.net> (raw)
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...
Rob
-------------------------------------------------------
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
next reply other threads:[~2005-10-09 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 5:54 Rob Landley [this message]
2005-10-09 19:06 ` [uml-devel] Found the problem Blaisorblade
2005-10-09 22:37 ` Rob Landley
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=200510090054.07750.rob@landley.net \
--to=rob@landley.net \
--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