From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] sendfile06_64 failure on i386
Date: Wed, 20 Aug 2014 18:37:48 +0200 [thread overview]
Message-ID: <20140820163748.GC23887@rei> (raw)
In-Reply-To: <2040651060.10018391.1408550993826.JavaMail.zimbra@redhat.com>
Hi!
> this testcase is currently failing on i386:
>
> sendfile06_64 1 TFAIL : sendfile06.c:90: sendfile(2) failed to return expected value, expected: 17592186044442, got: 26
>
> It's using SAFE_FSTAT from libltp, which is not compiled with
> -D_FILE_OFFSET_BITS=64 -DOFF_T=__off64_t as the testcase.
>
> The testcase can pass if I turn SAFE_FSTAT into plain fstat:
>
> - SAFE_FSTAT(cleanup, fd, &sb);
> + TEST(fstat(fd, &sb));
> + if (TEST_RETURN != 0)
> + tst_brkm(TBROK | TTERRNO, cleanup, "fstat");
>
> but I'm wondering if we can fix this at global level, so users
> of safe_macros don't have to worry about this.
I guess that turning the safe_fstat() into static inline function and
putting it into the safe_macros.h header should fix the issue. That way
the fstat would use struct stat64 corectly if corresponding macros are
defined.
Anything else would need more ifdefs and would be fairly tricky to
maintain.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
parent reply other threads:[~2014-08-20 16:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2040651060.10018391.1408550993826.JavaMail.zimbra@redhat.com>]
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=20140820163748.GC23887@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@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