From: shuah at kernel.org (shuah)
Subject: [PATCHv2] selftests/efivarfs: clean up test files from test_create*()
Date: Fri, 19 Apr 2019 07:19:52 -0600 [thread overview]
Message-ID: <03bdc88d-07cd-08ca-7d2f-ba93069eb41b@kernel.org> (raw)
In-Reply-To: <20190419131221.28297-1-po-hsu.lin@canonical.com>
On 4/19/19 7:12 AM, Po-Hsu Lin wrote:
> Test files created by test_create*() tests will stay in the
> $efivarfs_mount directory unless the system was rebooted.
>
> When the tester tries to run this efivarfs test again on the same
> system, the immutable characteristics in that directory will cause some
> "Operation not permitted" noises and a false-positve test result to the
> test_create_read() test.
>
> --------------------
> running test_create
> --------------------
> ./efivarfs.sh: line 59: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Operation not permitted
> [PASS]
> --------------------
> running test_create_empty
> --------------------
> ./efivarfs.sh: line 78: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Operation not permitted
> [PASS]
> --------------------
> running test_create_read
> --------------------
> open(O_WRONLY): Operation not permitted
> [FAIL]
> --------------------
>
> Create a file_cleanup() to remove those test files in the end of each
> test to solve this issue.
>
> Also, use this function to replace the existing file removal code.
>
> Link: https://bugs.launchpad.net/bugs/1809704
>
> Signed-off-by: Po-Hsu Lin <po-hsu.lin at canonical.com>
> ---
Thanks for the patch. There is another patch that does the same in
linux-kselftest next branch.
Please check to see if that fixes the problem you are seeing.
thanks,
-- Shuah
WARNING: multiple messages have this Message-ID (diff)
From: shuah@kernel.org (shuah)
Subject: [PATCHv2] selftests/efivarfs: clean up test files from test_create*()
Date: Fri, 19 Apr 2019 07:19:52 -0600 [thread overview]
Message-ID: <03bdc88d-07cd-08ca-7d2f-ba93069eb41b@kernel.org> (raw)
Message-ID: <20190419131952.WKzSQS7HPrq0et5YqTcS240SZhLQvweUkUgnSSHRfRo@z> (raw)
In-Reply-To: <20190419131221.28297-1-po-hsu.lin@canonical.com>
On 4/19/19 7:12 AM, Po-Hsu Lin wrote:
> Test files created by test_create*() tests will stay in the
> $efivarfs_mount directory unless the system was rebooted.
>
> When the tester tries to run this efivarfs test again on the same
> system, the immutable characteristics in that directory will cause some
> "Operation not permitted" noises and a false-positve test result to the
> test_create_read() test.
>
> --------------------
> running test_create
> --------------------
> ./efivarfs.sh: line 59: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Operation not permitted
> [PASS]
> --------------------
> running test_create_empty
> --------------------
> ./efivarfs.sh: line 78: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Operation not permitted
> [PASS]
> --------------------
> running test_create_read
> --------------------
> open(O_WRONLY): Operation not permitted
> [FAIL]
> --------------------
>
> Create a file_cleanup() to remove those test files in the end of each
> test to solve this issue.
>
> Also, use this function to replace the existing file removal code.
>
> Link: https://bugs.launchpad.net/bugs/1809704
>
> Signed-off-by: Po-Hsu Lin <po-hsu.lin at canonical.com>
> ---
Thanks for the patch. There is another patch that does the same in
linux-kselftest next branch.
Please check to see if that fixes the problem you are seeing.
thanks,
-- Shuah
WARNING: multiple messages have this Message-ID (diff)
From: shuah <shuah@kernel.org>
To: Po-Hsu Lin <po-hsu.lin@canonical.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah <shuah@kernel.org>
Subject: Re: [PATCHv2] selftests/efivarfs: clean up test files from test_create*()
Date: Fri, 19 Apr 2019 07:19:52 -0600 [thread overview]
Message-ID: <03bdc88d-07cd-08ca-7d2f-ba93069eb41b@kernel.org> (raw)
In-Reply-To: <20190419131221.28297-1-po-hsu.lin@canonical.com>
On 4/19/19 7:12 AM, Po-Hsu Lin wrote:
> Test files created by test_create*() tests will stay in the
> $efivarfs_mount directory unless the system was rebooted.
>
> When the tester tries to run this efivarfs test again on the same
> system, the immutable characteristics in that directory will cause some
> "Operation not permitted" noises and a false-positve test result to the
> test_create_read() test.
>
> --------------------
> running test_create
> --------------------
> ./efivarfs.sh: line 59: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Operation not permitted
> [PASS]
> --------------------
> running test_create_empty
> --------------------
> ./efivarfs.sh: line 78: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Operation not permitted
> [PASS]
> --------------------
> running test_create_read
> --------------------
> open(O_WRONLY): Operation not permitted
> [FAIL]
> --------------------
>
> Create a file_cleanup() to remove those test files in the end of each
> test to solve this issue.
>
> Also, use this function to replace the existing file removal code.
>
> Link: https://bugs.launchpad.net/bugs/1809704
>
> Signed-off-by: Po-Hsu Lin <po-hsu.lin@canonical.com>
> ---
Thanks for the patch. There is another patch that does the same in
linux-kselftest next branch.
Please check to see if that fixes the problem you are seeing.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-04-19 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 13:12 [PATCHv2] selftests/efivarfs: clean up test files from test_create*() po-hsu.lin
2019-04-19 13:12 ` Po-Hsu Lin
2019-04-19 13:12 ` Po-Hsu Lin
2019-04-19 13:19 ` shuah [this message]
2019-04-19 13:19 ` shuah
2019-04-19 13:19 ` shuah
2019-04-19 13:30 ` po-hsu.lin
2019-04-19 13:30 ` Po-Hsu Lin
2019-04-19 13:30 ` Po-Hsu Lin
2019-04-19 13:40 ` shuah
2019-04-19 13:40 ` shuah
2019-04-19 13:40 ` shuah
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=03bdc88d-07cd-08ca-7d2f-ba93069eb41b@kernel.org \
--to=unknown@example.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 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.