From: Yafang Shao <laoar.shao@gmail.com>
To: KP Singh <kpsingh@kernel.org>
Cc: akpm@linux-foundation.org, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, omosnace@redhat.com,
mhocko@suse.com, ying.huang@intel.com, linux-mm@kvack.org,
linux-security-module@vger.kernel.org, bpf@vger.kernel.org,
ligang.bdlg@bytedance.com
Subject: Re: [PATCH v4 5/5] selftests/bpf: Add selftests for set_mempolicy with a lsm prog
Date: Wed, 13 Dec 2023 11:08:00 +0800 [thread overview]
Message-ID: <CALOAHbCfrvLhbJAMKip+G2hxhiyYB5b3we+ovKjWhovggJ2deQ@mail.gmail.com> (raw)
In-Reply-To: <CACYkzJ7Eg=bG5Vr8eiXyLq+hto2KpnzhgRrw3eiJiqeJSs4w_w@mail.gmail.com>
On Wed, Dec 13, 2023 at 3:22 AM KP Singh <kpsingh@kernel.org> wrote:
>
> On Fri, Dec 8, 2023 at 10:06 AM Yafang Shao <laoar.shao@gmail.com> wrote:
> >
> > The result as follows,
> > #263/1 set_mempolicy/MPOL_BIND_without_lsm:OK
> > #263/2 set_mempolicy/MPOL_DEFAULT_without_lsm:OK
> > #263/3 set_mempolicy/MPOL_BIND_with_lsm:OK
> > #263/4 set_mempolicy/MPOL_DEFAULT_with_lsm:OK
> > #263 set_mempolicy:OK
> > Summary: 1/4 PASSED, 0 SKIPPED, 0 FAILED
>
> Please write a commit description on what the test actually does. I
will do it.
> even think of something simple that mentions a BPF LSM program that
> denies all mbind with the mode MPOL_BIND and checks whether the
> corresponding syscall is denied when the program is loaded.
It does. Additionally, it verifies whether the mbind syscall is denied
with different modes, such as MPOL_DEFAULT."
--
Regards
Yafang
prev parent reply other threads:[~2023-12-13 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231208090622.4309-1-laoar.shao@gmail.com>
[not found] ` <20231208090622.4309-4-laoar.shao@gmail.com>
2023-12-08 17:30 ` [PATCH v4 3/5] mm, security: Add lsm hook for memory policy adjustment Casey Schaufler
2023-12-10 2:54 ` Yafang Shao
[not found] ` <20231208090622.4309-6-laoar.shao@gmail.com>
2023-12-12 19:22 ` [PATCH v4 5/5] selftests/bpf: Add selftests for set_mempolicy with a lsm prog KP Singh
2023-12-13 3:08 ` Yafang Shao [this message]
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=CALOAHbCfrvLhbJAMKip+G2hxhiyYB5b3we+ovKjWhovggJ2deQ@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=jmorris@namei.org \
--cc=kpsingh@kernel.org \
--cc=ligang.bdlg@bytedance.com \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=ying.huang@intel.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