public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] read/read02.c: add new error number tests
Date: Mon, 5 May 2014 13:53:04 +0200	[thread overview]
Message-ID: <20140505115303.GA9027@rei> (raw)
In-Reply-To: <1399262735.3177.14.camel@G08JYZSD130126>

Hi!
> > > +	tst_require_root(NULL);
> > 
> > Does O_DIRECT require root?
> > (I haven't found anything in read man page that would suggests so)
> > 
> 
> In fedora20, /tmp is tmpfs.
> This test will fail if open a file with O_DIRECT in /tmp, like:
> read02      1  TBROK  :  open failed at read02.c:147: errno=EINVAL(22):
> Invalid argument
> So I test it in /root.

That is wrong way to solve this problem.

> > There is no need to unlink files if you call tst_rmdir(). You only need
> > to close filedescriptors.
> > 
> 
> TEST_FILE4 is not in /tmp.

The test should create all files in a directory created by tst_tmpdir().

We should handle this as:

* Skip the test (TCONF) if temp diretory is tmpfs (does not support O_DIRECT)
  (see include/tst_fs_type.h)

* User should pass alternative temp directory to runltp script to make
  the test working in case /tmp is on tmpfs

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2014-05-05 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  7:20 [LTP] [PATCH] read/read02.c: cleanup Zeng Linggang
2014-03-28  7:22 ` [LTP] [PATCH] read/read02.c: add new error number tests Zeng Linggang
2014-04-29 16:31   ` chrubis
     [not found]     ` <1399262735.3177.14.camel@G08JYZSD130126>
2014-05-05 11:53       ` chrubis [this message]
     [not found]         ` <1399362493.3177.40.camel@G08JYZSD130126>
     [not found]           ` <1399362582.3177.41.camel@G08JYZSD130126>
2014-05-26 13:37             ` [LTP] [PATCH v2 1/3] SAFE_MACROS: Add memalign() chrubis
     [not found]           ` <1399362661.3177.43.camel@G08JYZSD130126>
2014-05-26 13:37             ` [LTP] [PATCH v2 2/3] read/read02.c: cleanup chrubis
     [not found]           ` <1399362721.3177.44.camel@G08JYZSD130126>
2014-05-26 13:39             ` [LTP] [PATCH v2 3/3] read/read02.c: add new error number tests chrubis
2014-05-26 13:44             ` chrubis
     [not found]               ` <1401171983.23078.0.camel@G08JYZSD130126>
2014-05-27 16:41                 ` [LTP] [PATCH] read/read02.c: fix skipping all testes on tmpfs chrubis
2014-04-29 16:10 ` [LTP] [PATCH] read/read02.c: cleanup 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=20140505115303.GA9027@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=zenglg.jy@cn.fujitsu.com \
    /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