All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: ltp@lists.linux.it
Subject: [LTP] LTP: mount02 was expected EINVAL(22) but got ENOENT(2): No such file or directory
Date: Wed, 13 Mar 2019 19:17:00 +0530	[thread overview]
Message-ID: <CA+G9fYudJC07HfrU1fVptCEvgCuBsF9G2N76PiGG5Z258z0Dzg@mail.gmail.com> (raw)

LTP syscalls mount02 failed on mainline (Linux version 5.0.0) for all devices.

Results comparison link,
https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/ltp-syscalls-tests/mount02
you could see good and bad commit id in the above link.

Error log,
mount02 5 TFAIL : mount02.c:117: mount() was expected to fail with
EINVAL(22): TEST_ERRNO=ENOENT(2): No such file or directory

Failure full log on x15 armv7,
https://lkft.validation.linaro.org/scheduler/job/638009#L7462

structure Inputs,
{&null, &mntpoint, &fs_type, 0, EINVAL, NULL, NULL},

Snippet  test code:
--------------------------
TEST(mount(*tc->device, *tc->mntpoint, *tc->fs_type, tc->flag, NULL));

if (TEST_RETURN != -1) {
tst_resm(TFAIL, "mount() succeded unexpectedly (ret=%li)",
         TEST_RETURN);
goto cleanup;
}

if (TEST_ERRNO != tc->exp_errno) {
tst_resm(TFAIL | TTERRNO,
         "mount() was expected to fail with %s(%i)",
         tst_strerrno(tc->exp_errno), tc->exp_errno);
goto cleanup;
}

do you notice this mount02 failure on mainline kernel ?

Best regards
Naresh Kamboju

             reply	other threads:[~2019-03-13 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 13:47 Naresh Kamboju [this message]
2019-03-13 15:29 ` [LTP] LTP: mount02 was expected EINVAL(22) but got ENOENT(2): No such file or directory Jan Stancek
2019-03-14  5:18   ` Naresh Kamboju
2019-03-14  8:23     ` Jan Stancek
2019-04-18  7:14       ` Xiao Yang
2019-04-18  7:24         ` Al Viro
2019-04-18  7:35           ` Xiao Yang

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=CA+G9fYudJC07HfrU1fVptCEvgCuBsF9G2N76PiGG5Z258z0Dzg@mail.gmail.com \
    --to=naresh.kamboju@linaro.org \
    --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 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.