From: Xiong Zhou <xzhou@redhat.com>
To: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v3 1/3] fcntl14: dup code clean up
Date: Thu, 25 Sep 2014 23:23:49 -0400 (EDT) [thread overview]
Message-ID: <1096621493.37297301.1411701829900.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5424057E.2000407@oracle.com>
----- Original Message -----
> From: "Stanislav Kholmanskikh" <stanislav.kholmanskikh@oracle.com>
> To: "Xiong Zhou" <xzhou@redhat.com>
> Cc: ltp-list@lists.sourceforge.net
> Sent: Thursday, September 25, 2014 8:07:26 PM
> Subject: Re: [LTP] [PATCH v3 1/3] fcntl14: dup code clean up
>
> Hi!
>
> On 09/25/2014 11:17 AM, Xiong Zhou wrote:
> >
> > And block3 description message fix from "mandatory locking"
> > to "negative whence".
> >
> > Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> > ---
>
> Patch 1 and patch 2 of the series are pushed.
> Btw, patch 2 didn't apply to index correctly with 'git am', I had to
> manually apply it.
>
Sorry for the inconvenience.. I should keep my master branch updated.
> I'm experiencing difficulties with checking patch 3. In particular,
> after applying your patch utime02 fails on NFSv4 with
> 2.6.32-431.29.2.el6.x86_64 kernel.
Yes, I got the same results on 2.6.32-431.29.2.el6 kernel, v3 pass v4 fail.
>
> I'm not quite sure if it's a kernel problem or test case error. Still
> investigating.
>
> Could you please check the test case in your RHEL 6 environment as well?
I double checked that utime02 did pass on upstream 2.6.32 kernel
both NFSv3 and NFSv4 in my env.
On latest RHEL-6 kernel, both NFSv3 and NFSv4 passed utime02 test case.
All failed test_output are just like:
tst_tmpdir.c:158: chown(/nfsmnt/ltp-6L6Oqow6wv/utiMPq3y5, -1, 0) \
failed: errno=EPERM(1): Operation not permitted
One single clean chown(nfsfile, -1, 0) call to NFSv3/4 file succeeds
on multiple kernels include 2.6.32-431.29.2.el6.
Neither, I'm not sure about where the problem lies. Still checking.
Thanks for catching this!
--
xzhou
>
> Thank you.
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-09-26 3:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1397094487.31209591.1410431434756.JavaMail.zimbra@redhat.com>
2014-09-11 10:30 ` [LTP] [PATCH 1/3] fcntl14: dup code clean up Xiong Zhou
2014-09-11 14:04 ` Stanislav Kholmanskikh
2014-09-19 6:46 ` Xiong Zhou
2014-09-23 11:52 ` Stanislav Kholmanskikh
2014-09-19 6:47 ` [LTP] [PATCH v2 " Xiong Zhou
2014-09-25 7:17 ` [LTP] [PATCH v3 " Xiong Zhou
2014-09-25 12:07 ` Stanislav Kholmanskikh
2014-09-26 3:23 ` Xiong Zhou [this message]
2014-09-26 12:36 ` Stanislav Kholmanskikh
2014-09-28 2:53 ` Xiong Zhou
2014-09-29 8:28 ` Stanislav Kholmanskikh
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=1096621493.37297301.1411701829900.JavaMail.zimbra@redhat.com \
--to=xzhou@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=stanislav.kholmanskikh@oracle.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