qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Scordino <claudio@evidence.eu.com>
To: qemu-devel@nongnu.org
Cc: michael trimarchi <michael@evidence.eu.com>
Subject: [Qemu-devel] fstat bug on armeb stll exists!
Date: Thu, 29 Nov 2007 14:43:35 +0100	[thread overview]
Message-ID: <474EC207.1030700@evidence.eu.com> (raw)

Hi all,

   more than one year ago we sent a patch on this mailing list to fix 
a problem of the fstat syscall for armeb. See

http://lists.gnu.org/archive/html/qemu-devel/2006-09/msg00137.html

We found the bug compiling a Linux kernel for armeb on scratchbox.

Qemu seemed to ignore the fact that in big endian systems the fields
st_blocks and its padding are swapped (to allow future expansion of 
the field,) so the fix consisted only in swapping the two fields (only 
in big endian systems, of course).

The patch just changed  qemu/linux-user/syscall_defs.h to

#ifndef TARGET_WORDS_BIGENDIAN
        target_ulong    st_blocks;
        target_ulong    __pad4;
#else
       target_ulong    __pad4;
       target_ulong    st_blocks;
#endif

I've just dowloaded a fresh 0.9 Qemu, and I saw that there is still 
the bug...

Do you mind integrate such change, so we don't have to patch Qemu any 
time ?

Regards,

         Claudio Scordino



-- 
=================================
Claudio Scordino		
Software Engineer

Evidence Srl
Embedded Real-Time solutions
http://www.evidence.eu.com
=================================

             reply	other threads:[~2007-11-29 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 13:43 Claudio Scordino [this message]
2007-12-02  7:12 ` [Qemu-devel] fstat bug on armeb stll exists! Thiemo Seufer

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=474EC207.1030700@evidence.eu.com \
    --to=claudio@evidence.eu.com \
    --cc=michael@evidence.eu.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).