All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] open12 failing on i386 with EOVERFLOW
Date: Wed, 20 Aug 2014 08:56:21 -0400 (EDT)	[thread overview]
Message-ID: <663056555.9870858.1408539381311.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1070499573.9869577.1408539206966.JavaMail.zimbra@redhat.com>





----- Original Message -----
> From: "Jan Stancek" <jstancek@redhat.com>
> To: "ltp-list" <ltp-list@lists.sf.net>
> Sent: Wednesday, 20 August, 2014 2:53:26 PM
> Subject: [LTP] open12 failing on i386 with EOVERFLOW
> 
> Hi,
> 
> I'm seeing following failure in this testcase on RHEL-6.5 Server i386 GA
> distro:
> 
> # env PATH=`pwd`:$PATH ./open12
> open12      1  TFAIL  :  open12.c:104: test O_APPEND for open failed
> open12      2  TCONF  :  open12.c:123: test O_NOATIME flag for open needs
> filesystems which is mounted without noatime and relatime
> open12      3  TPASS  :  test O_CLOEXEC for open success
> open12      4  TPASS  :  test O_LARGEFILE for open success
> open12      0  TWARN  :  tst_tmpdir.c:206: tst_rmdir: rmobj(/tmp/opexIqjV3)
> failed: lstat(/tmp/opexIqjV3/large_file) failed; errno=75: Value too large
> for defined data type
> 

Same issue in openat02:

# env PATH=`pwd`:$PATH ./openat02
openat02    1  TPASS  :  test O_APPEND for openat success
openat02    2  TPASS  :  test O_CLOEXEC for openat success
openat02    3  TPASS  :  test O_LARGEFILE for openat success
openat02    4  TCONF  :  openat02.c:242: test O_NOATIME flag for openat needs filesystems which are mounted without noatime and relatime
openat02    5  TPASS  :  test O_NOFOLLOW for openat success
openat02    6  TPASS  :  test O_TRUNC for openat success
openat02    0  TWARN  :  tst_tmpdir.c:206: tst_rmdir: rmobj(/tmp/opeim4IKK) failed: lstat(/tmp/opeim4IKK/large_file) failed; errno=75: Value too large for defined data type


> Since it's linked from library, adding -D_FILE_OFFSET_BITS=64 to this
> testcase has
> no effect.
> 
> One simple way to fix it would be to unlink it in test, so that
> rmobj.c doesn't hit it.
> 
> $ diff -u open12.c /tmp/open12.c
> --- open12.c	2014-08-14 17:46:33.052044613 +0200
> +++ /tmp/open12.c	2014-08-20 14:48:35.655208417 +0200
> @@ -221,6 +221,10 @@
>  		tst_resm(TPASS, "test O_LARGEFILE for open success");
>  		SAFE_CLOSE(cleanup, TEST_RETURN);
>  	}
> +
> +	/* clean it up here, because lib/rmobj.c on 32bit will
> +	 * hit EOVERFLOW in lstat() */
> +	unlink(LARGE_FILE);
>  }
>  
>  static void cleanup(void)
> 
> Any thoughts?
> 
> Regards,
> Jan
> 
> ------------------------------------------------------------------------------
> 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
> 

------------------------------------------------------------------------------
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

  reply	other threads:[~2014-08-20 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <933677084.9868450.1408538960160.JavaMail.zimbra@redhat.com>
2014-08-20 12:53 ` [LTP] open12 failing on i386 with EOVERFLOW Jan Stancek
2014-08-20 12:56   ` Jan Stancek [this message]
2014-08-20 14:19   ` chrubis
     [not found]     ` <1919467615.10002040.1408549666554.JavaMail.zimbra@redhat.com>
2014-08-20 15:54       ` chrubis
     [not found]       ` <1317036748.10807258.1408632581704.JavaMail.zimbra@redhat.com>
2014-08-21 15:33         ` chrubis

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=663056555.9870858.1408539381311.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp-list@lists.sf.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.