Messages in this thread |  | | From | KP Singh <> | Date | Fri, 27 Nov 2020 14:09:33 +0100 | Subject | Re: [PATCH bpf-next v3 3/3] bpf: Add a selftest for bpf_ima_inode_hash |
| |
On Fri, Nov 27, 2020 at 5:29 AM Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote: > > On Tue, Nov 24, 2020 at 7:16 AM KP Singh <kpsingh@chromium.org> wrote: > > > > From: KP Singh <kpsingh@google.com> > >
[...]
> > > +cleanup() { > > + local tmp_dir="$1" > > + local mount_img="${tmp_dir}/test.img" > > + local mount_dir="${tmp_dir}/mnt" > > + > > + local loop_devices=$(losetup -j ${mount_img} -O NAME --noheadings) > > libbpf and kernel-patches CIs are using BusyBox environment which has > losetup that doesn't support -j option. Is there some way to work > around that? What we have is this: > > BusyBox v1.31.1 () multi-call binary. > > Usage: losetup [-rP] [-o OFS] {-f|LOOPDEV} FILE: associate loop devices > > losetup -c LOOPDEV: reread file size > > losetup -d LOOPDEV: disassociate > > losetup -a: show status
I can try to grep and parse the status output as a fallback. Will send another fix.
- KP
> > losetup -f: show next free loop device > > -o OFS Start OFS bytes into FILE > > -P Scan for partitions > > -r Read-only > > -f Show/use next free loop device > > > > + for loop_dev in "${loop_devices}"; do
[...]
|  |