lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMsOgNC=WmrrKfF2w6JxZj98dvNN05VyjLHBGA6kjFXog4rxzg@mail.gmail.com>
Date:   Fri, 12 Apr 2019 23:08:11 +0100
From:   Jiong Wang <jiong.wang@...ronome.com>
To:     Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>
Cc:     Jakub Kicinski <jakub.kicinski@...ronome.com>, bpf@...r.kernel.org,
        Networking <netdev@...r.kernel.org>, oss-drivers@...ronome.com
Subject: Re: [PATCH/RFC v2 bpf-next 11/19] libbpf: new global variable "libbpf_test_mode"

> If we want a more clean change in libbpf, it is more about how to offer clean API to
> pass "prog_flags" when load file/obj/raw_insn,

I followed this path a little bit further:
  - naturally allow specify prog_flags through *_attr structure.
  - set high 32-bit randomization prog_flags through macro direct.

Now, the global variable in libbpf removed, all tests in selftests are
still enabled
with hi32 randomization and the code changes on testsuites also is little.

Not sure if the idea is good, changes included in v3.

Regards,
Jiong

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ