20 Jan, 2021

8 commits

  • This is the 5.10.9 stable release

    * tag 'v5.10.9': (153 commits)
    Linux 5.10.9
    netfilter: nf_nat: Fix memleak in nf_nat_init
    netfilter: conntrack: fix reading nf_conntrack_buckets
    ...

    Signed-off-by: Jason Liu

    Jason Liu
     
  • This is the 5.10.8 stable release

    * tag 'v5.10.8': (104 commits)
    Linux 5.10.8
    tools headers UAPI: Sync linux/fscrypt.h with the kernel sources
    drm/panfrost: Remove unused variables in panfrost_job_close()
    ...

    Signed-off-by: Jason Liu

    Jason Liu
     
  • This is the 5.10.7 stable release

    * tag 'v5.10.7': (144 commits)
    Linux 5.10.7
    scsi: target: Fix XCOPY NAA identifier lookup
    rtlwifi: rise completion at the last step of firmware callback
    ...

    Signed-off-by: Jason Liu

    Jason Liu
     
  • This is the 5.10.5 stable release

    * tag 'v5.10.5': (63 commits)
    Linux 5.10.5
    device-dax: Fix range release
    ext4: avoid s_mb_prefetch to be zero in individual scenarios
    ...

    Signed-off-by: Jason Liu

    Jason Liu
     
  • commit fab336b42441e0b2eb1d81becedb45fbdf99606e upstream.

    Fix nft_conntrack_helper.sh false fail report:

    1) Conntrack tool need "-f ipv6" parameter to show out ipv6 traffic items.

    2) Sleep 1 second after background nc send packet, to make sure check
    is after this statement executed.

    False report:
    FAIL: ns1-lkjUemYw did not show attached helper ip set via ruleset
    PASS: ns1-lkjUemYw connection on port 2121 has ftp helper attached
    ...

    After fix:
    PASS: ns1-2hUniwU2 connection on port 2121 has ftp helper attached
    PASS: ns2-2hUniwU2 connection on port 2121 has ftp helper attached
    ...

    Fixes: 619ae8e0697a6 ("selftests: netfilter: add test case for conntrack helper assignment")
    Signed-off-by: Chen Yi
    Signed-off-by: Pablo Neira Ayuso
    Signed-off-by: Greg Kroah-Hartman

    Chen Yi
     
  • commit 5501e9229a80d95a1ea68609f44c447a75d23ed5 upstream.

    In some cases, the number of cpus (nr_cpus_online) is confused with the
    maximum cpu number (nr_cpus_avail), which results in the error in the
    example below:

    Example on system with 8 cpus:

    Before:
    # echo 0 > /sys/devices/system/cpu/cpu2/online
    # ./perf record --kcore -e intel_pt// taskset --cpu-list 7 uname
    Linux
    [ perf record: Woken up 1 times to write data ]
    [ perf record: Captured and wrote 0.147 MB perf.data ]
    # ./perf script --itrace=e
    Requested CPU 7 too large. Consider raising MAX_NR_CPUS
    0x25908 [0x8]: failed to process type: 68 [Invalid argument]

    After:
    # ./perf script --itrace=e
    #

    Fixes: 8c7274691f0d ("perf machine: Replace MAX_NR_CPUS with perf_env::nr_cpus_online")
    Fixes: 7df4e36a4785 ("perf session: Replace MAX_NR_CPUS with perf_env::nr_cpus_online")
    Signed-off-by: Adrian Hunter
    Tested-by: Kan Liang
    Cc: Jiri Olsa
    Cc: stable@vger.kernel.org
    Link: http://lore.kernel.org/lkml/20210107174159.24897-1-adrian.hunter@intel.com
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Greg Kroah-Hartman

    Adrian Hunter
     
  • [ Upstream commit 3503ee6c0bec5f173d606359e6384a5ef85492fb ]

    The udpgro.sh will always return 0 (unless the bpf selftest was not
    build first) even if there are some failed sub test-cases.

    Therefore the kselftest framework will report this case is OK.

    Check and return the exit status of each test to make it easier to
    spot real failures.

    Signed-off-by: Po-Hsu Lin
    Signed-off-by: David S. Miller
    Signed-off-by: Sasha Levin

    Po-Hsu Lin
     
  • commit 55ed4560774d81d7343223b8fd2784c530a9c6c1 upstream.

    Add ftrace.instance.INSTANCE.tracing_on support to ftrace2bconf.sh
    and bconf2ftrace.sh.

    commit 8490db06f914 ("tracing/boot: Add per-instance tracing_on
    option support") added the per-instance tracing_on option,
    but forgot to update the helper scripts.

    Link: https://lkml.kernel.org/r/160749166410.3497930.14204335886811029800.stgit@devnote2

    Cc: stable@vger.kernel.org
    Fixes: 8490db06f914 ("tracing/boot: Add per-instance tracing_on option support")
    Signed-off-by: Masami Hiramatsu
    Signed-off-by: Steven Rostedt (VMware)
    Signed-off-by: Greg Kroah-Hartman

    Masami Hiramatsu
     

17 Jan, 2021

5 commits

  • commit 4a443a51776ca9847942523cf987a330894d3a31 upstream.

    To pick the changes from:

    3ceb6543e9cf6ed8 ("fscrypt: remove kernel-internal constants from UAPI header")

    That don't result in any changes in tooling, just addressing this perf
    build warning:

    Warning: Kernel ABI header at 'tools/include/uapi/linux/fscrypt.h' differs from latest version at 'include/uapi/linux/fscrypt.h'
    diff -u tools/include/uapi/linux/fscrypt.h include/uapi/linux/fscrypt.h

    Cc: Adrian Hunter
    Cc: Eric Biggers
    Cc: Ian Rogers
    Cc: Jiri Olsa
    Cc: Namhyung Kim
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Greg Kroah-Hartman

    Arnaldo Carvalho de Melo
     
  • commit a5c9ca76a1c61fb5e4c35de8eb25aa925b03c9e4 upstream.

    For IPv6 traffic, mausezahn needs to be invoked with '-6'. Otherwise an
    error is returned:

    # ip netns exec me mausezahn veth1 -B 2001:db8:101::2 -A 2001:db8:91::1 -c 0 -t tcp "dp=1-1023, flags=syn"
    Failed to set source IPv4 address. Please check if source is set to a valid IPv4 address.
    Invalid command line parameters!

    Fixes: 7c741868ceab ("selftests: Add torture tests to nexthop tests")
    Signed-off-by: Ido Schimmel
    Reviewed-by: Petr Machata
    Reviewed-by: David Ahern
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Greg Kroah-Hartman

    Ido Schimmel
     
  • commit 6f02b540d7597f357bc6ee711346761045d4e108 upstream.

    For older glibc ~2.17, #include'ing both linux/if.h and net/if.h
    fails due to complaints about redefinition of interface flags:

    CC net.o
    In file included from net.c:13:0:
    /usr/include/linux/if.h:71:2: error: redeclaration of enumerator ‘IFF_UP’
    IFF_UP = 1< resolves the issue and it is
    not needed for compilation anyhow.

    [1] https://lore.kernel.org/netdev/1461512707-23058-1-git-send-email-mikko.rapeli__34748.27880641$1462831734$gmane$org@iki.fi/

    Fixes: f6f3bac08ff9 ("tools/bpf: bpftool: add net support")
    Signed-off-by: Alan Maguire
    Signed-off-by: Andrii Nakryiko
    Acked-by: Martin KaFai Lau
    Link: https://lore.kernel.org/bpf/1609948746-15369-1-git-send-email-alan.maguire@oracle.com
    Signed-off-by: Greg Kroah-Hartman

    Alan Maguire
     
  • commit 1a3449c19407a28f7019a887cdf0d6ba2444751a upstream.

    If Makefile cannot find any of the vmlinux's in its VMLINUX_BTF_PATHS list,
    it tries to run btftool incorrectly, with VMLINUX_BTF unset:

    bpftool btf dump file $(VMLINUX_BTF) format c

    Such that the keyword 'format' is misinterpreted as the path to vmlinux.
    The resulting build error message is fairly cryptic:

    GEN vmlinux.h
    Error: failed to load BTF from format: No such file or directory

    This patch makes the failure reason clearer by yielding this instead:

    Makefile:...: *** Cannot find a vmlinux for VMLINUX_BTF at any of
    "{paths}". Stop.

    Fixes: acbd06206bbb ("selftests/bpf: Add vmlinux.h selftest exercising tracing of syscalls")
    Signed-off-by: Kamal Mostafa
    Signed-off-by: Andrii Nakryiko
    Link: https://lore.kernel.org/bpf/20201215182011.15755-1-kamal@canonical.com
    Signed-off-by: Greg Kroah-Hartman

    Kamal Mostafa
     
  • [ Upstream commit 5316a7c0130acf09bfc8bb0092407006010fcccc ]

    Adds new 2 new tests to the PTMU script: pmtu_ipv4/6_route_change.

    These tests explicitly test for a recently discovered problem in the
    IPv6 routing framework where PMTU exceptions were not properly released
    when replacing a route via "ip route change ...".

    After creating PMTU exceptions, the route from the device A to R1 will be
    replaced with a new route, then device A will be deleted. If the PMTU
    exceptions were properly cleaned up by the kernel, this device deletion
    will succeed. Otherwise, the unregistration of the device will stall, and
    messages such as the following will be logged in dmesg:

    unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 4

    Signed-off-by: Sean Tranchetti
    Reviewed-by: David Ahern
    Link: https://lore.kernel.org/r/1609892546-11389-2-git-send-email-stranche@quicinc.com
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Greg Kroah-Hartman

    Sean Tranchetti
     

13 Jan, 2021

2 commits

  • [ Upstream commit 7cf22a1c88c05ea3807f95b1edfebb729016ae52 ]

    Commit d8cbe8bfa7d ("tools/testing/selftests/vm: fix build error") tried
    to include a ARCH check for powerpc, however ARCH is not defined in the
    Makefile before including lib.mk. This makes test building to skip on
    both x86 and powerpc.

    Fix the arch check by replacing it using machine type as it is already
    defined and used in the test.

    Link: https://lkml.kernel.org/r/20201215100402.257376-1-harish@linux.ibm.com
    Fixes: d8cbe8bfa7d ("tools/testing/selftests/vm: fix build error")
    Signed-off-by: Harish
    Reviewed-by: Sandipan Das
    Cc: Shuah Khan
    Cc: Sandipan Das
    Cc: John Hubbard
    Cc: Dave Hansen
    Cc: Kirill A. Shutemov
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds
    Signed-off-by: Sasha Levin

    Harish
     
  • [ Upstream commit 2ff2c7e274392871bfdee00ff2adbb8ebae5d240 ]

    The test was setting the headroom size of the wrong port. This was not
    visible because of a firmware bug that canceled this bug.

    Set the headroom size of the correct port, so that the test will pass
    with both old and new firmware versions.

    Fixes: bfa804784e32 ("selftests: mlxsw: Add a PFC test")
    Signed-off-by: Ido Schimmel
    Reviewed-by: Petr Machata
    Link: https://lore.kernel.org/r/20201230114251.394009-1-idosch@idosch.org
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Greg Kroah-Hartman

    Ido Schimmel
     

06 Jan, 2021

1 commit

  • commit 7ddcdea5b54492f54700f427f58690cf1e187e5e upstream.

    To pick up the changes in:

    a85cbe6159ffc973 ("uapi: move constants from to ")

    That causes no changes in tooling, just addresses this perf build
    warning:

    Warning: Kernel ABI header at 'tools/include/uapi/linux/const.h' differs from latest version at 'include/uapi/linux/const.h'
    diff -u tools/include/uapi/linux/const.h include/uapi/linux/const.h

    Cc: Adrian Hunter
    Cc: Ian Rogers
    Cc: Jiri Olsa
    Cc: Namhyung Kim
    Cc: Petr Vorel
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Greg Kroah-Hartman

    Arnaldo Carvalho de Melo
     

04 Jan, 2021

2 commits

  • This is the 5.10.4 stable release

    * tag 'v5.10.4': (717 commits)
    Linux 5.10.4
    x86/CPU/AMD: Save AMD NodeId as cpu_die_id
    drm/edid: fix objtool warning in drm_cvt_modes()
    ...

    Signed-off-by: Jason Liu

    Conflicts:
    drivers/gpu/drm/imx/dcss/dcss-plane.c
    drivers/media/i2c/ov5640.c

    Jason Liu
     
  • This is the 5.10.2 stable release

    * tag 'v5.10.2': (17 commits)
    Linux 5.10.2
    serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
    ALSA: pcm: oss: Fix potential out-of-bounds shift
    ...

    Signed-off-by: Jason Liu

    Conflicts:
    drivers/usb/host/xhci-hub.c
    drivers/usb/host/xhci.h

    Jason Liu
     

30 Dec, 2020

12 commits

  • [ Upstream commit 5149303fdfe5c67ddb51c911e23262f781cd75eb ]

    The argv_split() function must be paired with argv_free(), else we must
    keep a reference to the argv array received or do the freeing ourselves,
    in synthesize_sdt_probe_command() we were simply leaking that argv[]
    array.

    Fixes: 3b1f8311f6963cd1 ("perf probe: Add sdt probes arguments into the uprobe cmd string")
    Cc: Adrian Hunter
    Cc: Alexander Shishkin
    Cc: Alexandre Truong
    Cc: Alexis Berlemont
    Cc: He Zhe
    Cc: Ian Rogers
    Cc: Ingo Molnar
    Cc: Jiri Olsa
    Cc: John Garry
    Cc: Mark Rutland
    Cc: Masami Hiramatsu
    Cc: Mathieu Poirier
    Cc: Namhyung Kim
    Cc: Peter Zijlstra
    Cc: Sumanth Korikkar
    Cc: Thomas Richter
    Cc: Will Deacon
    Link: https://lore.kernel.org/r/20201224135139.GF477817@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Sasha Levin

    Arnaldo Carvalho de Melo
     
  • [ Upstream commit 2eb5dd418034ecea2f7031e3d33f2991a878b148 ]

    When using 'perf record's option '-I' or '--user-regs=' along with
    argument '?' to list available register names, memory of variable 'os'
    allocated by strdup() needs to be released before __parse_regs()
    returns, otherwise memory leak will occur.

    Fixes: bcc84ec65ad1 ("perf record: Add ability to name registers to record")
    Signed-off-by: Zheng Zengkai
    Acked-by: Jiri Olsa
    Cc: Alexander Shishkin
    Cc: Li Bin
    Cc: Mark Rutland
    Cc: Namhyung Kim
    Link: https://lore.kernel.org/r/20200703093344.189450-1-zhengzengkai@huawei.com
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Sasha Levin

    Zheng Zengkai
     
  • [ Upstream commit 09d59c2f3465fb01e65a0c96698697b026ea8e79 ]

    We're missing -lcap in test-all.bin target, so in case it's the only
    library missing (if more are missing test-all.bin fails anyway), we will
    falsely claim that we detected it and fail build, like:

    $ make
    ...
    Auto-detecting system features:
    ... dwarf: [ on ]
    ... dwarf_getlocations: [ on ]
    ... glibc: [ on ]
    ... libbfd: [ on ]
    ... libbfd-buildid: [ on ]
    ... libcap: [ on ]
    ... libelf: [ on ]
    ... libnuma: [ on ]
    ... numa_num_possible_cpus: [ on ]
    ... libperl: [ on ]
    ... libpython: [ on ]
    ... libcrypto: [ on ]
    ... libunwind: [ on ]
    ... libdw-dwarf-unwind: [ on ]
    ... zlib: [ on ]
    ... lzma: [ on ]
    ... get_cpuid: [ on ]
    ... bpf: [ on ]
    ... libaio: [ on ]
    ... libzstd: [ on ]
    ... disassembler-four-args: [ on ]

    ...

    CC builtin-ftrace.o

    In file included from builtin-ftrace.c:29:
    util/cap.h:11:10: fatal error: sys/capability.h: No such file or directory
    11 | #include
    | ^~~~~~~~~~~~~~~~~~
    compilation terminated.

    Fixes: 74d5f3d06f707eb5 ("tools build: Add capability-related feature detection")
    Signed-off-by: Jiri Olsa
    Cc: Alexander Shishkin
    Cc: Ian Rogers
    Cc: Igor Lubashev
    Cc: Mark Rutland
    Cc: Michael Petlan
    Cc: Namhyung Kim
    Cc: Peter Zijlstra
    Cc: Stephane Eranian
    Link: http://lore.kernel.org/lkml/20201203230836.3751981-1-jolsa@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Sasha Levin

    Jiri Olsa
     
  • [ Upstream commit b2ce5dbc15819ea4bef47dbd368239cb1e965158 ]

    Commit e1c92a7fbbc5 ("perf tests: Add another metric parsing test") add
    another test for metric parsing. The test goes through all metrics
    compiled for arch within pmu events and try to parse them.

    Right now this test is failing in powerpc machine.

    Result in power9 platform:

    [command]# ./perf test 10
    10: PMU events :
    10.1: PMU event table sanity : Ok
    10.2: PMU event map aliases : Ok
    10.3: Parsing of PMU event table metrics : Skip (some metrics failed)
    10.4: Parsing of PMU event table metrics with fake PMUs : FAILED!

    Issue is we are passing different runtime parameter value in
    "expr__find_other" and "expr__parse" function which is called from
    function `metric_parse_fake`. And because of this parsing of hv-24x7
    metrics is failing.

    [command]# ./perf test 10 -vv
    .....
    hv_24x7/pm_mcs01_128b_rd_disp_port01,chip=1/ not found
    expr__parse failed
    test child finished with -1
    ---- end ----
    PMU events subtest 4: FAILED!

    This patch fix this issue and change runtime parameter value to '0' in
    expr__parse function.

    Result in power9 platform after this patch:

    [command]# ./perf test 10
    10: PMU events :
    10.1: PMU event table sanity : Ok
    10.2: PMU event map aliases : Ok
    10.3: Parsing of PMU event table metrics : Skip (some metrics failed)
    10.4: Parsing of PMU event table metrics with fake PMUs : Ok

    Fixes: e1c92a7fbbc5 ("perf tests: Add another metric parsing test")
    Signed-off-by: Kajol Jain
    Acked-by: Ian Rogers
    Acked-by: Jiri Olsa
    Cc: Madhavan Srinivasan
    Cc: Ravi Bangoria
    Link: http://lore.kernel.org/lkml/20201119152411.46041-1-kjain@linux.ibm.com
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Sasha Levin

    Kajol Jain
     
  • [ Upstream commit eceae70bdeaeb6b8ceb662983cf663ff352fbc96 ]

    strncat()'s third argument is how many bytes will be added *in addition* to
    already existing bytes in destination. Plus extra zero byte will be added
    after that. So existing use in test_sockmap has many opportunities to overflow
    the string and cause memory corruptions. And in this case, GCC complains for
    a good reason.

    Fixes: 16962b2404ac ("bpf: sockmap, add selftests")
    Fixes: 73563aa3d977 ("selftests/bpf: test_sockmap, print additional test options")
    Fixes: 1ade9abadfca ("bpf: test_sockmap, add options for msg_pop_data() helper")
    Fixes: 463bac5f1ca7 ("bpf, selftests: Add test for ktls with skb bpf ingress policy")
    Fixes: e9dd904708c4 ("bpf: add tls support for testing in test_sockmap")
    Fixes: 753fb2ee0934 ("bpf: sockmap, add msg_peek tests to test_sockmap")
    Signed-off-by: Andrii Nakryiko
    Signed-off-by: Alexei Starovoitov
    Link: https://lore.kernel.org/bpf/20201203235440.2302137-2-andrii@kernel.org
    Signed-off-by: Sasha Levin

    Andrii Nakryiko
     
  • [ Upstream commit 9cf309c56f7910a81fbe053b6f11c3b1f0987b12 ]

    When we added sanitising of map names before loading programs to libbpf, we
    still allowed periods in the name. While the kernel will accept these for
    the map names themselves, they are not allowed in file names when pinning
    maps. This means that bpf_object__pin_maps() will fail if called on an
    object that contains internal maps (such as sections .rodata).

    Fix this by replacing periods with underscores when constructing map pin
    paths. This only affects the paths generated by libbpf when
    bpf_object__pin_maps() is called with a path argument. Any pin paths set
    by bpf_map__set_pin_path() are unaffected, and it will still be up to the
    caller to avoid invalid characters in those.

    Fixes: 113e6b7e15e2 ("libbpf: Sanitise internal map names so they are not rejected by the kernel")
    Signed-off-by: Toke Høiland-Jørgensen
    Signed-off-by: Andrii Nakryiko
    Link: https://lore.kernel.org/bpf/20201203093306.107676-1-toke@redhat.com
    Signed-off-by: Sasha Levin

    Toke Høiland-Jørgensen
     
  • [ Upstream commit 2c07343abd8932200a45ff7b10950e71081e9e77 ]

    seccomp_bpf.c uses unshare(CLONE_NEWPID), which requires CONFIG_PID_NS
    to be set.

    Cc: Kees Cook
    Cc: Shuah Khan
    Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
    Signed-off-by: Mickaël Salaün
    Acked-by: Tycho Andersen
    Signed-off-by: Kees Cook
    Link: https://lore.kernel.org/r/20201202162643.249276-1-mic@digikod.net
    Signed-off-by: Sasha Levin

    Mickaël Salaün
     
  • [ Upstream commit 6016df8fe874e1cf36f6357d71438b384198ce06 ]

    The selftests/bpf Makefile includes system include directories from
    the host, when building BPF programs. On RISC-V glibc requires that
    __riscv_xlen is defined. This is not the case for "clang -target bpf",
    which messes up __WORDSIZE (errno.h -> ... -> wordsize.h) and breaks
    the build.

    By explicitly defining __risc_xlen correctly for riscv, we can
    workaround this.

    Fixes: 167381f3eac0 ("selftests/bpf: Makefile fix "missing" headers on build with -idirafter")
    Signed-off-by: Björn Töpel
    Signed-off-by: Andrii Nakryiko
    Acked-by: Luke Nelson
    Link: https://lore.kernel.org/bpf/20201118071640.83773-2-bjorn.topel@gmail.com
    Signed-off-by: Sasha Levin

    Björn Töpel
     
  • [ Upstream commit 58cfa49c2ba7f815adccc27a775e7cf8a8f7f539 ]

    In comment 173ca26e9b51 ("samples/bpf: add comprehensive ipip, ipip6,
    ip6ip6 test") we added ip6ip6 test for bpf tunnel testing. But in commit
    933a741e3b82 ("selftests/bpf: bpf tunnel test.") when we moved it to
    the current folder, we didn't add it.

    This patch add the ip6ip6 test back to bpf tunnel test. Update the ipip6's
    topology for both IPv4 and IPv6 testing. Since iperf test is removed as
    currect framework simplified it in purpose, I also removed unused tcp
    checkings in test_tunnel_kern.c.

    Fixes: 933a741e3b82 ("selftests/bpf: bpf tunnel test.")
    Signed-off-by: Hangbin Liu
    Signed-off-by: Alexei Starovoitov
    Link: https://lore.kernel.org/bpf/20201110015013.1570716-2-liuhangbin@gmail.com
    Signed-off-by: Sasha Levin

    Hangbin Liu
     
  • [ Upstream commit 93f20eff0cca972d74cb554a2e8b47730228be16 ]

    Should be -d instead of -n for dry-run.

    Fixes: 5da1918446a1 ("selftests/run_kselftest.sh: Make each test individually selectable")
    Signed-off-by: Hangbin Liu
    Signed-off-by: Shuah Khan
    Signed-off-by: Sasha Levin

    Hangbin Liu
     
  • [ Upstream commit f0e5ba0bc481df77cf0afac2b33e420b33eeb463 ]

    The {inode,sk}_storage_result checking if the correct value was retrieved
    was being clobbered unconditionally by the return value of the
    bpf_{inode,sk}_storage_delete call.

    Also, consistently use the newly added BPF_LOCAL_STORAGE_GET_F_CREATE
    flag.

    Fixes: cd324d7abb3d ("bpf: Add selftests for local_storage")
    Signed-off-by: KP Singh
    Signed-off-by: Alexei Starovoitov
    Acked-by: Song Liu
    Link: https://lore.kernel.org/bpf/20201106103747.2780972-7-kpsingh@chromium.org
    Signed-off-by: Sasha Levin

    KP Singh
     
  • [ Upstream commit 9b0a7836359443227c9af101f7aea8412e739458 ]

    I found that the UNHALTED_CORE_CYCLES event is only available in the
    Intel machines and it makes other vendors/archs fail on the test. As
    libpfm4 can parse the generic events like cycles, let's use them.

    Fixes: 40b74c30ffb9 ("perf test: Add expand cgroup event test")
    Signed-off-by: Namhyung Kim
    Acked-by: Ian Rogers
    Cc: Alexander Shishkin
    Cc: Andi Kleen
    Cc: Jiri Olsa
    Cc: Mark Rutland
    Cc: Peter Zijlstra
    Cc: Stephane Eranian
    Link: http://lore.kernel.org/lkml/20201027072855.655449-1-namhyung@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Sasha Levin

    Namhyung Kim
     

21 Dec, 2020

2 commits

  • commit 170f4869e66275f498ae4736106fb54c0fdcd036 upstream.

    The logic for truncating the log file for emailing based on the
    MAIL_MAX_SIZE option is confusing and incorrect. Simplify it and have the
    tail of the log file truncated to the max size specified in the config.

    Cc: stable@vger.kernel.org
    Fixes: 855d8abd2e8ff ("ktest.pl: Change the logic to control the size of the log file emailed")
    Signed-off-by: Steven Rostedt (VMware)
    Signed-off-by: Greg Kroah-Hartman

    Steven Rostedt (VMware)
     
  • commit 8cd6bc0359deebd8500e6de95899a8a78d3ec4ba upstream.

    If the size of the error log is too big to send via email, and the sending
    fails, it wont email any result. This can be confusing for the user who is
    waiting for an email on the completion of the tests.

    If it fails to send email, then try again without the log file stating that
    it failed to send an email. Obviously this will not be of use if the sending
    of email failed for some other reasons, but it will at least give the user
    some information when it fails for the most common reason.

    Cc: stable@vger.kernel.org
    Fixes: c2d84ddb338c8 ("ktest.pl: Add MAIL_COMMAND option to define how to send email")
    Signed-off-by: Steven Rostedt (VMware)
    Signed-off-by: Greg Kroah-Hartman

    Steven Rostedt (VMware)
     

18 Dec, 2020

1 commit

  • * perf/next: (19 commits)
    MLK-23418-7 perf vendor events: add JSON metrics for imx8dxl DDR/DB Perf
    MLK-23418-4 perf/imx_ddr: Add driver support for i.MX8DXL DB Perf
    MLK-23418-3 perf/imx_ddr: Add clock support for Perf in DB
    MLK-23418-2 docs/perf: update ddr perf guide for PMU in DB
    MLK-23418-1 perf/imx_ddr: Extend driver for PMU in DRAM Block(DB)
    ...

    BJ DevOps Team
     

14 Dec, 2020

7 commits