From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Nicolas Joly <njoly@pasteur.fr>
Cc: LTP list <ltp-list@lists.sf.net>
Subject: Re: [LTP] ftruncate04.c: cleanup mandatory locking check
Date: Wed, 12 May 2010 22:53:07 +0530 [thread overview]
Message-ID: <1273684988.4910.5.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20100512131426.GA190127@medusa.sis.pasteur.fr>
On Wed, 2010-05-12 at 15:14 +0200, Nicolas Joly wrote:
> Hi,
>
> The attached patch tries to cleanup the `mandatory locking' check in
> the ftruncate04.c testcase.
>
> The currently test is made with system(2) and involve calling some
> external tools ... to determine if the underlying filesystem has
> `mand' option set. The same result can be easily retrieved with a
> simple statvfs(2) call and examining the mount flags value.
>
> This has been successfully tested on a RHEL5 x86_64 machine.
>
> Signed-off-by: Nicolas Joly <njoly@pasteur.fr>
Thanks. This does not introduce any regression. Will wait for others
comments as well.
Regards--
Subrata
>
> Regards.
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-05-12 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 13:14 [LTP] ftruncate04.c: cleanup mandatory locking check Nicolas Joly
2010-05-12 17:23 ` Subrata Modak [this message]
2010-05-17 20:06 ` Subrata Modak
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=1273684988.4910.5.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sf.net \
--cc=njoly@pasteur.fr \
/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