From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Subject: Re: x86_64: 32bit emulation problems
Date: Tue, 1 Mar 2005 00:43:00 +0100 [thread overview]
Message-ID: <200503010043.01078.bernd-schubert@web.de> (raw)
In-Reply-To: <1109629608.13407.30.camel@lade.trondhjem.org>
On Monday 28 February 2005 23:26, you wrote:
> Given that strace shows that both syscalls (stat64() and stat())
> succeed, I expect the "problem" is probably just glibc setting an
> EOVERFLOW error in the 32-bit case. That's what it is supposed to do if
> a 64 bit value overflows the 32-bit buffers.
Right, thanks.
>
> Have you tried looking at errno?
>
bernd@hitchcock tests>./test_stat32 /mnt/test/yp
stat for /mnt/test/yp failed
ernno: 75 (Value too large for defined data type)
But why does stat64() on a 64-bit kernel tries to fill in larger data than on
a 32-bit kernel and larger data also only for nfs-mount points? Hmm, I will
tomorrow compare the tcp-packges sent by the server.
Many thanks,
Bernd
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-28 23:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 21:08 x86_64: 32bit emulation problems Bernd Schubert
2005-02-28 22:26 ` Trond Myklebust
2005-02-28 23:14 ` Bernd Schubert
2005-02-28 23:43 ` Bernd Schubert [this message]
2005-03-01 0:47 ` Dan Stromberg
-- strict thread matches above, loose matches on Subject: below --
2005-02-28 20:54 Bernd Schubert
2005-02-28 21:00 ` Bernd Schubert
2005-03-01 20:24 ` Andi Kleen
2005-03-01 21:07 ` Bernd Schubert
2005-03-01 21:07 ` Bernd Schubert
2005-03-01 21:48 ` Andi Kleen
2005-03-01 22:30 ` Bernd Schubert
2005-03-01 22:30 ` Bernd Schubert
2005-03-01 23:07 ` Andi Kleen
2005-03-01 22:10 ` Andreas Schwab
2005-03-01 22:10 ` Andreas Schwab
2005-03-01 22:19 ` Andi Kleen
2005-03-01 23:22 ` Andreas Schwab
2005-03-01 23:22 ` Andreas Schwab
2005-03-01 23:19 ` Bernd Schubert
2005-03-01 23:39 ` Andreas Schwab
2005-03-01 23:39 ` Andreas Schwab
2005-03-01 23:46 ` Andreas Schwab
2005-03-01 23:46 ` Andreas Schwab
2005-03-02 8:18 ` Andi Kleen
2005-03-02 9:13 ` Trond Myklebust
2005-03-02 11:33 ` Bernd Schubert
2005-03-02 16:53 ` Trond Myklebust
2005-03-02 18:14 ` Bernd Schubert
2005-03-03 9:19 ` Andi Kleen
2005-03-03 21:16 ` Bernd Schubert
2005-03-03 21:32 ` Andi Kleen
2005-03-03 21:37 ` Trond Myklebust
2005-03-03 21:46 ` Andi Kleen
2005-03-03 22:21 ` Trond Myklebust
2005-03-03 9:12 ` Andi Kleen
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=200503010043.01078.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.