From: Shuah Khan <skhan@linuxfoundation.org>
To: SeongJae Park <sj38.park@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
Gautam <gautammenghani201@gmail.com>,
shuah@kernel.org, damon@lists.linux.dev, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4] kselftests/damon: add support for cases where debugfs cannot be read
Date: Mon, 27 Jun 2022 13:46:58 -0600 [thread overview]
Message-ID: <5708a2f6-4555-7bb3-4664-c33fe5b411b1@linuxfoundation.org> (raw)
In-Reply-To: <20220627185704.58902-1-sj38.park@gmail.com>
On 6/27/22 12:57 PM, SeongJae Park wrote:
> From: SeongJae Park <sj@kernel.org>
>
> Hi Shuah,
>
> On Mon, 27 Jun 2022 11:00:18 -0600 Shuah Khan <skhan@linuxfoundation.org> wrote:
>
> [...]
>>>> --- a/tools/testing/selftests/damon/_chk_dependency.sh
>>>> +++ b/tools/testing/selftests/damon/_chk_dependency.sh
>>>> @@ -26,3 +26,13 @@ do
>>>> exit 1
>>>> fi
>>>> done
>>>> +
>>>> +permission_error="Operation not permitted"
>>>> +for f in attrs target_ids monitor_on
>>>> +do
>>>> + status=$( cat "$DBGFS/$f" 2>&1 )
>>>> + if [ "${status#*$permission_error}" != "$status" ]; then
>>>> + echo "Permission for reading $DBGFS/$f denied; maybe secureboot enabled?"
>>
>> btw - does this run as a regular user or does it need root privilege?
>> If so add a test for that and skip with a message.
>
> It needs the root permission, and does the check at the beginning[1].
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/damon/_chk_dependency.sh?h=v5.19-rc4#n9
>
>
Great. Thank you. I will pull this one in for linux-kselftest next
for Linux 5.20-rc1
thanks,
-- Shuah
next prev parent reply other threads:[~2022-06-27 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 19:52 [PATCH] kselftests/damon: add support for checking secureboot status Gautam
2022-06-24 20:29 ` SeongJae Park
2022-06-25 5:56 ` [PATCH v2] kselftests/damon: add support for cases where debugfs cannot be read Gautam
2022-06-25 8:35 ` [PATCH v3] " Gautam
2022-06-25 18:55 ` SeongJae Park
2022-06-25 19:52 ` [PATCH v4] " Gautam
2022-06-25 20:03 ` SeongJae Park
2022-06-27 17:00 ` Shuah Khan
2022-06-27 18:57 ` SeongJae Park
2022-06-27 19:46 ` Shuah Khan [this message]
[not found] ` <Yrn6BxU298rzjiak@fedora>
2022-06-28 3:37 ` Gautam Menghani
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=5708a2f6-4555-7bb3-4664-c33fe5b411b1@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=damon@lists.linux.dev \
--cc=gautammenghani201@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sj@kernel.org \
/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