From: Andi Kleen <ak@muc.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Bernd Schubert <bernd-schubert@web.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
nfs@lists.sourceforge.net
Subject: Re: x86_64: 32bit emulation problems
Date: 1 Mar 2005 23:19:02 +0100
Date: Tue, 1 Mar 2005 23:19:02 +0100 [thread overview]
Message-ID: <20050301221902.GA73844@muc.de> (raw)
In-Reply-To: <jewtsruie9.fsf@sykes.suse.de>
On Tue, Mar 01, 2005 at 11:10:38PM +0100, Andreas Schwab wrote:
> That's because there are some values in the stat64 buffer delivered by the
> kernel which cannot be packed into the stat buffer that you pass to stat.
> Use stat64 or _FILE_OFFSET_BITS=64.
If that had been the case strace would have reported EOVERFLOW
or E2BIG. But it returned 0 according to the log that was posted.
-Andi
next prev parent reply other threads:[~2005-03-01 22:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 20:54 x86_64: 32bit emulation problems 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:48 ` Andi Kleen
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:19 ` Andi Kleen [this message]
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: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=20050301221902.GA73844@muc.de \
--to=ak@muc.de \
--cc=bernd-schubert@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=schwab@suse.de \
/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