From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA-32 emulation issues
Date: Thu, 02 Jan 2003 23:31:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805633@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805630@msgid-missing>
David Mosberger <davidm@napali.hpl.hp.com> writes:
>
> Arun> b) getdents64 - the system call succeeds, but glibc sets EOVERFLOW. We
> Arun> may want to think about getting rid of "struct linux32_dirent" at
> Arun> some point.
>
> Arun> History from glibc sources:
>
> Arun> /* The getdents64 syscall was introduced in 2.4.0-test7. We test for
> Arun> 2.4.1 for the earliest version we know the syscall is available. */
> Arun> #if __LINUX_KERNEL_VERSION >= 132097
> Arun> # define __ASSUME_GETDENTS64_SYSCALL 1
> Arun> #endif
>
> If you muck with this, it'd probably be best to put it in fs/compat.c
> at the same time.
>
I've done some more debugging on this and I think there is no problem
with getdents/getdents64.
The problem was with a test case that did pwrite(2) with offset = -1
and it was expecting the test to fail. However, on IA-64, the test
case passed, leaving this temp file on the disk:
$ ls -l /tmp/pwrbcneW5/pwrite_file
-rw-r--r-- 1 tester tester 4294968319 Jan 2 15:34 /tmp/pwrbcneW5/pwrite_file
Subsequently, the test harness tries to cleanup the file and does a
lstat on it, which results in EOVERFLOW.
I'll follow up separately on the other two issues I raised.
-Arun
next prev parent reply other threads:[~2003-01-02 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 21:27 [Linux-ia64] IA-32 emulation issues Arun Sharma
2003-01-02 21:18 ` David Mosberger
2003-01-02 23:31 ` Arun Sharma [this message]
2003-01-02 23:38 ` David Mosberger
2003-01-08 17:42 ` Bjorn Helgaas
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=marc-linux-ia64-105590709805633@msgid-missing \
--to=arun.sharma@intel.com \
--cc=linux-ia64@vger.kernel.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 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.