All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] open12 failing on i386 with EOVERFLOW
Date: Wed, 20 Aug 2014 17:54:28 +0200	[thread overview]
Message-ID: <20140820155428.GA9005@rei> (raw)
In-Reply-To: <1919467615.10002040.1408549666554.JavaMail.zimbra@redhat.com>

Hi!
> > That is simple enough but I'm a bit reluctant to add the fix to each
> > test that will test O_LARGEFILE.
> > 
> > Given that the only purpose of lstat() in rmobj() is to figure out if
> > given path is a file or directory, we can try to work around this by
> > trying to opendir() the path first and treat it like a file when we get
> > ENOTDIR. What do you think?
> 
> I like the idea. I can try it tomorrow, unless you have patch ready.

Not yet, I've been working on enabling keyctl01 testcase that was
previously wrongly disabled by configure checks.

(It looks like the TCONF propagation is starting to pay off because
 it's far easier to spot and review skipped testcases.)

-- 
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 15:55 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
2014-08-20 14:19   ` chrubis
     [not found]     ` <1919467615.10002040.1408549666554.JavaMail.zimbra@redhat.com>
2014-08-20 15:54       ` chrubis [this message]
     [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=20140820155428.GA9005@rei \
    --to=chrubis@suse.cz \
    --cc=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.