From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
Date: Fri, 24 May 2019 10:59:47 +0200 [thread overview]
Message-ID: <20190524085947.GA11508@rei.lan> (raw)
In-Reply-To: <CAOQ4uxhHVG9f1njmPgei8-QO4UEivXbxoHkqKi4f50XN6Gup9A@mail.gmail.com>
Hi!
> > testcases/kernel/syscalls/fcntl/fcntl33.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/testcases/kernel/syscalls/fcntl/fcntl33.c b/testcases/kernel/syscalls/fcntl/fcntl33.c
> > index 43dc5a2af..627823c5c 100644
> > --- a/testcases/kernel/syscalls/fcntl/fcntl33.c
> > +++ b/testcases/kernel/syscalls/fcntl/fcntl33.c
> > @@ -117,7 +117,7 @@ static void do_test(unsigned int i)
> > if (TST_RET == -1) {
> > if (type == TST_OVERLAYFS_MAGIC && TST_ERR == EAGAIN) {
> > tst_res(TINFO | TTERRNO,
> > - "fcntl(F_SETLEASE, F_WRLCK) failed on overlapfs as expected");
> > + "fcntl(F_SETLEASE, F_WRLCK) failed on overlayfs as expected");
>
> You have 3 more of this typo in fcntl tests.
Ah, right, I should have done git grep before commiting this. I will fix
that right away.
> If you ask me, silencing this error seems wrong.
> While the error is *expected* it is still a broken interface.
> It may be just a matter of terminology, but I am reading this message as:
>
> TEST PASSED: Overlayfs failed as expected
>
> While it really should be more along the lines of:
>
> TEST SKIPPED: Overlayfs doesn't support write leased
Agreed, I'm always against working around kernel bugs/deficiencies in
tests, unfortunately that usually conflicts with QA deparenments that
wants to skip known problems and have everything green. So we usually
end up somewhere in a middle ground.
Also as usuall, do you care enough to send a patch? :-)
> Besides, this problem looks quite easy to fix.
> I think Bruce was already looking at changing the implementation of
> check_conflicting_open(), so if the test is not failing, nobody is going to
> nudge for a fix...
Once it's fixed we can change that to a failure for new enough kernels,
old ones should probably stay with SKIPPED/TCONF.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-05-24 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 13:45 [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs Cyril Hrubis
2019-05-23 15:42 ` Amir Goldstein
2019-05-23 16:46 ` J. Bruce Fields
2019-05-23 17:26 ` Amir Goldstein
2019-05-23 17:40 ` J. Bruce Fields
2019-05-23 20:01 ` Petr Vorel
2019-05-24 8:59 ` Cyril Hrubis [this message]
2019-05-24 11:03 ` Amir Goldstein
2019-05-24 13:45 ` Cyril Hrubis
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=20190524085947.GA11508@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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