* [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox
@ 2020-12-02 22:39 KP Singh
2020-12-02 22:39 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy KP Singh
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: KP Singh @ 2020-12-02 22:39 UTC (permalink / raw)
To: bpf; +Cc: Andrii Nakryiko, Alexei Starovoitov, Daniel Borkmann
From: KP Singh <kpsingh@google.com>
* losetup on busybox does not output the name of loop device on using
-f with --show. It also dosn't support -j to find the loop devices
for a given backing file. losetup is updated to use "-a" which is
available on busybox.
* blkid does not support options (-s and -o) to only display the uuid.
* Not all environments have mkfs.ext4, the test requires a loop device
with a backing image file which could formatted with any filesystem.
Update to using mkfs.ext2 which is available on busybox.
Fixes: 34b82d3ac105 ("bpf: Add a selftest for bpf_ima_inode_hash")
Reported-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: KP Singh <kpsingh@google.com>
---
tools/testing/selftests/bpf/ima_setup.sh | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/tools/testing/selftests/bpf/ima_setup.sh b/tools/testing/selftests/bpf/ima_setup.sh
index 15490ccc5e55..d864c62c1207 100755
--- a/tools/testing/selftests/bpf/ima_setup.sh
+++ b/tools/testing/selftests/bpf/ima_setup.sh
@@ -3,6 +3,7 @@
set -e
set -u
+set -o pipefail
IMA_POLICY_FILE="/sys/kernel/security/ima/policy"
TEST_BINARY="/bin/true"
@@ -23,13 +24,15 @@ setup()
dd if=/dev/zero of="${mount_img}" bs=1M count=10
- local loop_device="$(losetup --find --show ${mount_img})"
+ losetup -f "${mount_img}"
+ local loop_device=$(losetup -a | grep ${mount_img:?} | cut -d ":" -f1)
- mkfs.ext4 "${loop_device}"
+ mkfs.ext2 "${loop_device:?}"
mount "${loop_device}" "${mount_dir}"
cp "${TEST_BINARY}" "${mount_dir}"
- local mount_uuid="$(blkid -s UUID -o value ${loop_device})"
+ local mount_uuid="$(blkid ${loop_device} | sed 's/.*UUID="\([^"]*\)".*/\1/')"
+
echo "measure func=BPRM_CHECK fsuuid=${mount_uuid}" > ${IMA_POLICY_FILE}
}
@@ -38,7 +41,8 @@ cleanup() {
local mount_img="${tmp_dir}/test.img"
local mount_dir="${tmp_dir}/mnt"
- local loop_devices=$(losetup -j ${mount_img} -O NAME --noheadings)
+ local loop_devices=$(losetup -a | grep ${mount_img:?} | cut -d ":" -f1)
+
for loop_dev in "${loop_devices}"; do
losetup -d $loop_dev
done
--
2.29.2.576.ga3fc446d84-goog
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy
2020-12-02 22:39 [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox KP Singh
@ 2020-12-02 22:39 ` KP Singh
2020-12-02 22:44 ` KP Singh
2020-12-02 23:13 ` Andrii Nakryiko
2020-12-02 22:39 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add config dependency on BLK_DEV_LOOP KP Singh
2020-12-02 23:13 ` [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox Andrii Nakryiko
2 siblings, 2 replies; 9+ messages in thread
From: KP Singh @ 2020-12-02 22:39 UTC (permalink / raw)
To: bpf; +Cc: Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
From: KP Singh <kpsingh@google.com>
SecurityFS may not be mounted even if it is enabled in the kernel
config.
Signed-off-by: KP Singh <kpsingh@google.com>
---
tools/testing/selftests/bpf/ima_setup.sh | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/tools/testing/selftests/bpf/ima_setup.sh b/tools/testing/selftests/bpf/ima_setup.sh
index d864c62c1207..1da2d97a0e72 100755
--- a/tools/testing/selftests/bpf/ima_setup.sh
+++ b/tools/testing/selftests/bpf/ima_setup.sh
@@ -14,6 +14,20 @@ usage()
exit 1
}
+ensure_mount_securityfs()
+{
+ local securityfs_dir=$(grep "securityfs" /proc/mounts | awk '{print $2}')
+
+ if [ -z "${securityfs_dir}" ]; then
+ securityfs_dir=/sys/kernel/security
+ mount -t securityfs security "${securityfs_dir}"
+ fi
+
+ if [ ! -d "${securityfs_dir}" ]; then
+ echo "${securityfs_dir} :securityfs is not mounted" && exit 1
+ fi
+}
+
setup()
{
local tmp_dir="$1"
@@ -33,6 +47,7 @@ setup()
cp "${TEST_BINARY}" "${mount_dir}"
local mount_uuid="$(blkid ${loop_device} | sed 's/.*UUID="\([^"]*\)".*/\1/')"
+ ensure_mount_securityfs
echo "measure func=BPRM_CHECK fsuuid=${mount_uuid}" > ${IMA_POLICY_FILE}
}
--
2.29.2.576.ga3fc446d84-goog
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [PATCH bpf-next v2 3/3] selftests/bpf: Add config dependency on BLK_DEV_LOOP
2020-12-02 22:39 [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox KP Singh
2020-12-02 22:39 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy KP Singh
@ 2020-12-02 22:39 ` KP Singh
2020-12-02 22:43 ` KP Singh
2020-12-02 23:13 ` [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox Andrii Nakryiko
2 siblings, 1 reply; 9+ messages in thread
From: KP Singh @ 2020-12-02 22:39 UTC (permalink / raw)
To: bpf; +Cc: Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
From: KP Singh <kpsingh@google.com>
The ima selftest restricts its scope to a test filesystem image
mounted on a loop device and prevents permanent ima policy changes for
the whole system.
Signed-off-by: KP Singh <kpsingh@google.com>
---
tools/testing/selftests/bpf/config | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/bpf/config b/tools/testing/selftests/bpf/config
index 365bf9771b07..37e1f303fc11 100644
--- a/tools/testing/selftests/bpf/config
+++ b/tools/testing/selftests/bpf/config
@@ -43,3 +43,4 @@ CONFIG_IMA=y
CONFIG_SECURITYFS=y
CONFIG_IMA_WRITE_POLICY=y
CONFIG_IMA_READ_POLICY=y
+CONFIG_BLK_DEV_LOOP=y
--
2.29.2.576.ga3fc446d84-goog
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH bpf-next v2 3/3] selftests/bpf: Add config dependency on BLK_DEV_LOOP
2020-12-02 22:39 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add config dependency on BLK_DEV_LOOP KP Singh
@ 2020-12-02 22:43 ` KP Singh
0 siblings, 0 replies; 9+ messages in thread
From: KP Singh @ 2020-12-02 22:43 UTC (permalink / raw)
To: bpf; +Cc: Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
On Wed, Dec 2, 2020 at 11:39 PM KP Singh <kpsingh@chromium.org> wrote:
>
> From: KP Singh <kpsingh@google.com>
>
> The ima selftest restricts its scope to a test filesystem image
> mounted on a loop device and prevents permanent ima policy changes for
> the whole system.
>
> Signed-off-by: KP Singh <kpsingh@google.com>
Fixes: 34b82d3ac105 ("bpf: Add a selftest for bpf_ima_inode_hash")
Reported-by: Andrii Nakryiko <andrii@kernel.org>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy
2020-12-02 22:39 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy KP Singh
@ 2020-12-02 22:44 ` KP Singh
2020-12-02 23:13 ` Andrii Nakryiko
1 sibling, 0 replies; 9+ messages in thread
From: KP Singh @ 2020-12-02 22:44 UTC (permalink / raw)
To: bpf; +Cc: Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
On Wed, Dec 2, 2020 at 11:39 PM KP Singh <kpsingh@chromium.org> wrote:
>
> From: KP Singh <kpsingh@google.com>
>
> SecurityFS may not be mounted even if it is enabled in the kernel
> config.
>
> Signed-off-by: KP Singh <kpsingh@google.com>
Fixes: 34b82d3ac105 ("bpf: Add a selftest for bpf_ima_inode_hash")
Reported-by: Andrii Nakryiko <andrii@kernel.org>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox
2020-12-02 22:39 [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox KP Singh
2020-12-02 22:39 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy KP Singh
2020-12-02 22:39 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add config dependency on BLK_DEV_LOOP KP Singh
@ 2020-12-02 23:13 ` Andrii Nakryiko
2020-12-03 0:51 ` KP Singh
2 siblings, 1 reply; 9+ messages in thread
From: Andrii Nakryiko @ 2020-12-02 23:13 UTC (permalink / raw)
To: KP Singh; +Cc: bpf, Andrii Nakryiko, Alexei Starovoitov, Daniel Borkmann
On Wed, Dec 2, 2020 at 2:39 PM KP Singh <kpsingh@chromium.org> wrote:
>
> From: KP Singh <kpsingh@google.com>
>
> * losetup on busybox does not output the name of loop device on using
> -f with --show. It also dosn't support -j to find the loop devices
> for a given backing file. losetup is updated to use "-a" which is
> available on busybox.
> * blkid does not support options (-s and -o) to only display the uuid.
> * Not all environments have mkfs.ext4, the test requires a loop device
> with a backing image file which could formatted with any filesystem.
> Update to using mkfs.ext2 which is available on busybox.
>
> Fixes: 34b82d3ac105 ("bpf: Add a selftest for bpf_ima_inode_hash")
> Reported-by: Andrii Nakryiko <andrii@kernel.org>
> Signed-off-by: KP Singh <kpsingh@google.com>
> ---
Thanks for the fixes!
You have three related patches, please add a cover letter to the patch
set as well.
> tools/testing/selftests/bpf/ima_setup.sh | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/ima_setup.sh b/tools/testing/selftests/bpf/ima_setup.sh
> index 15490ccc5e55..d864c62c1207 100755
> --- a/tools/testing/selftests/bpf/ima_setup.sh
> +++ b/tools/testing/selftests/bpf/ima_setup.sh
> @@ -3,6 +3,7 @@
>
> set -e
> set -u
> +set -o pipefail
>
> IMA_POLICY_FILE="/sys/kernel/security/ima/policy"
> TEST_BINARY="/bin/true"
> @@ -23,13 +24,15 @@ setup()
>
> dd if=/dev/zero of="${mount_img}" bs=1M count=10
>
> - local loop_device="$(losetup --find --show ${mount_img})"
> + losetup -f "${mount_img}"
> + local loop_device=$(losetup -a | grep ${mount_img:?} | cut -d ":" -f1)
>
> - mkfs.ext4 "${loop_device}"
> + mkfs.ext2 "${loop_device:?}"
> mount "${loop_device}" "${mount_dir}"
>
> cp "${TEST_BINARY}" "${mount_dir}"
> - local mount_uuid="$(blkid -s UUID -o value ${loop_device})"
> + local mount_uuid="$(blkid ${loop_device} | sed 's/.*UUID="\([^"]*\)".*/\1/')"
tabs/spaces mix up here?
> +
> echo "measure func=BPRM_CHECK fsuuid=${mount_uuid}" > ${IMA_POLICY_FILE}
> }
>
> @@ -38,7 +41,8 @@ cleanup() {
> local mount_img="${tmp_dir}/test.img"
> local mount_dir="${tmp_dir}/mnt"
>
> - local loop_devices=$(losetup -j ${mount_img} -O NAME --noheadings)
> + local loop_devices=$(losetup -a | grep ${mount_img:?} | cut -d ":" -f1)
didn't know about :?, fancy
> +
> for loop_dev in "${loop_devices}"; do
> losetup -d $loop_dev
> done
> --
> 2.29.2.576.ga3fc446d84-goog
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy
2020-12-02 22:39 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy KP Singh
2020-12-02 22:44 ` KP Singh
@ 2020-12-02 23:13 ` Andrii Nakryiko
2020-12-03 0:49 ` KP Singh
1 sibling, 1 reply; 9+ messages in thread
From: Andrii Nakryiko @ 2020-12-02 23:13 UTC (permalink / raw)
To: KP Singh; +Cc: bpf, Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
On Wed, Dec 2, 2020 at 2:39 PM KP Singh <kpsingh@chromium.org> wrote:
>
> From: KP Singh <kpsingh@google.com>
>
> SecurityFS may not be mounted even if it is enabled in the kernel
> config.
>
> Signed-off-by: KP Singh <kpsingh@google.com>
> ---
please add those tags in v2 :)
> tools/testing/selftests/bpf/ima_setup.sh | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/ima_setup.sh b/tools/testing/selftests/bpf/ima_setup.sh
> index d864c62c1207..1da2d97a0e72 100755
> --- a/tools/testing/selftests/bpf/ima_setup.sh
> +++ b/tools/testing/selftests/bpf/ima_setup.sh
> @@ -14,6 +14,20 @@ usage()
> exit 1
> }
>
> +ensure_mount_securityfs()
> +{
> + local securityfs_dir=$(grep "securityfs" /proc/mounts | awk '{print $2}')
> +
> + if [ -z "${securityfs_dir}" ]; then
> + securityfs_dir=/sys/kernel/security
> + mount -t securityfs security "${securityfs_dir}"
> + fi
again, something is off with indentation here
> +
> + if [ ! -d "${securityfs_dir}" ]; then
> + echo "${securityfs_dir} :securityfs is not mounted" && exit 1
nit: " :" => ": " or it was intended this way?
> + fi
> +}
> +
> setup()
> {
> local tmp_dir="$1"
> @@ -33,6 +47,7 @@ setup()
> cp "${TEST_BINARY}" "${mount_dir}"
> local mount_uuid="$(blkid ${loop_device} | sed 's/.*UUID="\([^"]*\)".*/\1/')"
>
> + ensure_mount_securityfs
> echo "measure func=BPRM_CHECK fsuuid=${mount_uuid}" > ${IMA_POLICY_FILE}
> }
>
> --
> 2.29.2.576.ga3fc446d84-goog
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy
2020-12-02 23:13 ` Andrii Nakryiko
@ 2020-12-03 0:49 ` KP Singh
0 siblings, 0 replies; 9+ messages in thread
From: KP Singh @ 2020-12-03 0:49 UTC (permalink / raw)
To: Andrii Nakryiko; +Cc: bpf, Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
On Thu, Dec 3, 2020 at 12:13 AM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
>
> On Wed, Dec 2, 2020 at 2:39 PM KP Singh <kpsingh@chromium.org> wrote:
> >
> > From: KP Singh <kpsingh@google.com>
> >
> > SecurityFS may not be mounted even if it is enabled in the kernel
> > config.
> >
> > Signed-off-by: KP Singh <kpsingh@google.com>
> > ---
>
> please add those tags in v2 :)
Done.
>
> > tools/testing/selftests/bpf/ima_setup.sh | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/tools/testing/selftests/bpf/ima_setup.sh b/tools/testing/selftests/bpf/ima_setup.sh
> > index d864c62c1207..1da2d97a0e72 100755
> > --- a/tools/testing/selftests/bpf/ima_setup.sh
> > +++ b/tools/testing/selftests/bpf/ima_setup.sh
> > @@ -14,6 +14,20 @@ usage()
> > exit 1
> > }
> >
> > +ensure_mount_securityfs()
> > +{
> > + local securityfs_dir=$(grep "securityfs" /proc/mounts | awk '{print $2}')
> > +
> > + if [ -z "${securityfs_dir}" ]; then
> > + securityfs_dir=/sys/kernel/security
> > + mount -t securityfs security "${securityfs_dir}"
> > + fi
>
> again, something is off with indentation here
Yeah, changed it to spaces and added a patch at the end which changes
it to tabs.
Checkpatch did not catch it, maybe it ignores shell scripts :(
>
> > +
> > + if [ ! -d "${securityfs_dir}" ]; then
> > + echo "${securityfs_dir} :securityfs is not mounted" && exit 1
>
> nit: " :" => ": " or it was intended this way?
Fixes. Thanks.
>
>
> > + fi
> > +}
> > +
> > setup()
> > {
> > local tmp_dir="$1"
> > @@ -33,6 +47,7 @@ setup()
> > cp "${TEST_BINARY}" "${mount_dir}"
> > local mount_uuid="$(blkid ${loop_device} | sed 's/.*UUID="\([^"]*\)".*/\1/')"
> >
> > + ensure_mount_securityfs
> > echo "measure func=BPRM_CHECK fsuuid=${mount_uuid}" > ${IMA_POLICY_FILE}
> > }
> >
> > --
> > 2.29.2.576.ga3fc446d84-goog
> >
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox
2020-12-02 23:13 ` [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox Andrii Nakryiko
@ 2020-12-03 0:51 ` KP Singh
0 siblings, 0 replies; 9+ messages in thread
From: KP Singh @ 2020-12-03 0:51 UTC (permalink / raw)
To: Andrii Nakryiko; +Cc: bpf, Andrii Nakryiko, Alexei Starovoitov, Daniel Borkmann
On Thu, Dec 3, 2020 at 12:13 AM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
>
> On Wed, Dec 2, 2020 at 2:39 PM KP Singh <kpsingh@chromium.org> wrote:
> >
> > From: KP Singh <kpsingh@google.com>
> >
> > * losetup on busybox does not output the name of loop device on using
> > -f with --show. It also dosn't support -j to find the loop devices
> > for a given backing file. losetup is updated to use "-a" which is
> > available on busybox.
> > * blkid does not support options (-s and -o) to only display the uuid.
> > * Not all environments have mkfs.ext4, the test requires a loop device
> > with a backing image file which could formatted with any filesystem.
> > Update to using mkfs.ext2 which is available on busybox.
> >
> > Fixes: 34b82d3ac105 ("bpf: Add a selftest for bpf_ima_inode_hash")
> > Reported-by: Andrii Nakryiko <andrii@kernel.org>
> > Signed-off-by: KP Singh <kpsingh@google.com>
> > ---
>
> Thanks for the fixes!
>
> You have three related patches, please add a cover letter to the patch
> set as well.
Will do.
>
> > tools/testing/selftests/bpf/ima_setup.sh | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/tools/testing/selftests/bpf/ima_setup.sh b/tools/testing/selftests/bpf/ima_setup.sh
> > index 15490ccc5e55..d864c62c1207 100755
> > --- a/tools/testing/selftests/bpf/ima_setup.sh
> > +++ b/tools/testing/selftests/bpf/ima_setup.sh
> > @@ -3,6 +3,7 @@
> >
> > set -e
> > set -u
> > +set -o pipefail
> >
> > IMA_POLICY_FILE="/sys/kernel/security/ima/policy"
> > TEST_BINARY="/bin/true"
> > @@ -23,13 +24,15 @@ setup()
> >
> > dd if=/dev/zero of="${mount_img}" bs=1M count=10
> >
> > - local loop_device="$(losetup --find --show ${mount_img})"
> > + losetup -f "${mount_img}"
> > + local loop_device=$(losetup -a | grep ${mount_img:?} | cut -d ":" -f1)
> >
> > - mkfs.ext4 "${loop_device}"
> > + mkfs.ext2 "${loop_device:?}"
> > mount "${loop_device}" "${mount_dir}"
> >
> > cp "${TEST_BINARY}" "${mount_dir}"
> > - local mount_uuid="$(blkid -s UUID -o value ${loop_device})"
> > + local mount_uuid="$(blkid ${loop_device} | sed 's/.*UUID="\([^"]*\)".*/\1/')"
>
> tabs/spaces mix up here?
Yeah, it seems like the whole file is formatted with spaces and I
added tabs here. Added a patch
at the end of the series which reindents this. I have not added the
"Fixes" tag since it's not
a fix, do feel free to add it, if you think that's the norm for these
kinds of indentation fixes.
>
> > +
> > echo "measure func=BPRM_CHECK fsuuid=${mount_uuid}" > ${IMA_POLICY_FILE}
> > }
> >
> > @@ -38,7 +41,8 @@ cleanup() {
> > local mount_img="${tmp_dir}/test.img"
> > local mount_dir="${tmp_dir}/mnt"
> >
> > - local loop_devices=$(losetup -j ${mount_img} -O NAME --noheadings)
> > + local loop_devices=$(losetup -a | grep ${mount_img:?} | cut -d ":" -f1)
>
> didn't know about :?, fancy
Thanks :) It has helped me in rm -rf ${dir:?}/${file:?}
>
>
> > +
> > for loop_dev in "${loop_devices}"; do
> > losetup -d $loop_dev
> > done
> > --
> > 2.29.2.576.ga3fc446d84-goog
> >
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-12-03 0:52 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-02 22:39 [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox KP Singh
2020-12-02 22:39 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure securityfs mount before writing ima policy KP Singh
2020-12-02 22:44 ` KP Singh
2020-12-02 23:13 ` Andrii Nakryiko
2020-12-03 0:49 ` KP Singh
2020-12-02 22:39 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add config dependency on BLK_DEV_LOOP KP Singh
2020-12-02 22:43 ` KP Singh
2020-12-02 23:13 ` [PATCH bpf-next v2 1/3] selftests/bpf: Update ima_setup.sh for busybox Andrii Nakryiko
2020-12-03 0:51 ` KP Singh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).